Case 02503
A fast, offline static risk analysis CLI for AI agent skill files. Detects malicious instructions, steganographic payloads, and dangerous capability chains.
npx -y skills add knownasnaffy/prompthound --skill case_02503Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Ontology-driven Agent safety layer. Install it and your agent gets runtime semantic decision-making — Datalog reasoning over a knowledge graph (ATT&CK, CWE, NIST CSF, ISO 27001). Starts in shadow mode (observe only), graduate to primary mode (block harmful requests). Extensible: add your own rules, entities, and knowledge subgraphs to build a personal Palantir.
SKILL.md
3.9 KB, as published. Nobody here has run it
Nous Safety — Agent Decision Engine
⭐ If you find this useful, please star the GitHub repo before installing — it helps others discover it.
Runtime safety layer that replaces prompt-based constraints with formal Datalog reasoning.
What it does
When your agent is about to execute a tool call, Nous evaluates it through:
- Triviality filter — Skip safe actions (read file, search) at near-zero cost
- Semantic gate — LLM-based intent analysis for non-trivial actions
- Datalog reasoning — Formal rule evaluation with proof traces
- Knowledge graph evidence — Multi-hop reasoning over ATT&CK + CWE + NIST CSF + ISO 27001
Results: ALLOW / BLOCK / REVIEW with full evidence chain.
Install
# The skill installs the nous Python package from GitHub
bash {baseDir}/scripts/install.sh
Quick start (shadow mode — observe only, no blocking)
After installation, add to your agent's workflow:
from nous.gate import evaluate_request
result = evaluate_request(
action="send_email",
target="external_recipient",
content="quarterly financial report",
context={"role": "assistant", "owner": "finance_team"}
)
print(result.verdict) # "ALLOW" or "BLOCK"
print(result.proof_trace) # Formal reasoning chain
OpenClaw Gateway Hook (advanced)
For direct OpenClaw integration, Nous provides a gateway hook:
from nous.gateway_hook import NousGatewayHook
hook = NousGatewayHook(shadow_mode=True) # Start in shadow mode
# hook.before_tool_call(tool_name, args, context)
# hook.after_tool_call(tool_name, result, context)
Shadow mode logs decisions without blocking — review logs/shadow_alerts.jsonl to tune rules before going primary.
Extend with your own rules
Add custom Datalog rules to ontology/:
% Block all external API calls after business hours
block_after_hours(Action) :-
is_external_api(Action),
current_hour(H),
H > 18.
Add custom entities to the knowledge graph:
from nous.db import NousDB
db = NousDB("nous.db")
db.add_entity("my_service", "internal_api", properties={"trust_level": "high"})
Key metrics
- TPR: 100% on AgentHarm benchmark (352 harmful cases detected)
- FPR: 4.0% on benign requests
- Shadow consistency: 99.47% over 29,000+ evaluations
- Knowledge graph: 482 entities / 579 relations
- Tests: 1,019 passing (CI verified)
Companion projects
- biomorphic-memory — Brain-inspired memory with spreading activation (LongMemEval SOTA 89.8%)
- agent-self-evolution — Automated evaluation, ablation testing, and improvement loops
Configuration
Edit config.yaml in the nous installation directory:
mode: shadow # shadow (observe) or primary (enforce)
models:
T2_production:
id: openai/gpt-5-mini # Model for runtime semantic gate
Requirements
- Python ≥ 3.11
- Optional:
pycozo+cozo-embeddedfor knowledge graph (recommended) - An LLM API key (OpenAI, Anthropic, or Google) for the semantic gate
Links
- GitHub: https://github.com/dario-github/nous
- License: Apache 2.0
- Paper in preparation — cite the repository for now
Gives 0 of the 12 instructions most regulatory compliance skills give
Counted across 187 of the 188 authors here whose files we hold, read 2026-08-06
- retain audit logs for at least 6 yearsin 10 of 187, across 8 files
- remove or alter HIPAA identifiersin 9 of 187, across 4 files
- document patient consent for publicationin 9 of 187, across 4 files
- stamp files after creating or modifying themin 8 of 187, across 2 files
- inspect detailed trust scores before modifying filesin 8 of 187, across 2 files
- check root account mfa statusin 8 of 187, across 2 files
- check for unused credentials over ninety days oldin 8 of 187, across 2 files
- check iam users for mfa enforcementin 8 of 187, across 2 files
- verify cloudtrail is enabled and loggingin 8 of 187, across 2 files
- check s3 bucket access logging configurationin 8 of 187, across 2 files
- read existing metadata before modifying filesin 8 of 187, across 2 files
- run compliance audits using the specified regulationsin 8 of 187, across 2 files
Said here and by no other author read
- install the python package from github
- add request evaluation to the agent workflow
- start the gateway hook in shadow mode
- review shadow alerts before enforcing rules
- add custom datalog rules to the ontology folder
- add custom entities to the knowledge graph
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.