Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/waseemghanem98/agentcheck/agents-mdgit clone --depth 1 https://github.com/WaseemGhanem98/AgentCheckWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/waseemghanem98/agentcheck/agents-md)<a href="https://agentmods.dev/instructions/waseemghanem98/agentcheck/agents-md"><img src="https://agentmods.dev/badge/instructions/waseemghanem98/agentcheck/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01617 | $0.01617 |
| Opus 5 | $0.00809 | $0.00809 |
| Sonnet 5 | $0.00323 | $0.00323 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
AgentCheck AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working on AgentCheck
Instructions for AI coding agents and new contributors working in this
repository. Read this before changing anything under agentcheck/.
What this project is
AgentCheck is an evidence authority for AI-agent behavior, not a framework
compatibility layer. It imports a trusted local agent, derives adversarial
scenarios from what it finds, and runs them in same-user child processes where
declared tool calls are simulated. It emits PASS / FAIL / INCONCLUSIVE /
INFRA_ERROR, an HTML report, and a replay manifest.
The product's value is that its verdicts can be trusted. Every rule below exists to protect that.
Keep four evidence dimensions separate: contained, observed, semantically
understood, and policy-verifiable. One never implies the next. A blocked and
observed runtime action with unknown semantics remains INCONCLUSIVE, never a
PASS. Static discovery is lower-bounded, not exhaustive.
Non-negotiable invariants
Breaking any of these is a correctness bug, not a style issue:
- The original tool handler never executes during a simulated evaluation. Interception replaces the invoker before the handler is reached.
- Unknown tools fail closed. Never synthesize a tool result.
- No real mutations. Only the simulated world changes.
- Worker isolation. Scenarios run in child processes; the environment allowlist is empty by default. This is trusted-code process isolation, not a hostile-code sandbox.
- Network denied by default, and containment failures surface. The current Python guard is not a kernel security boundary and must not be described as one.
INCONCLUSIVEandINFRA_ERRORnever collapse intoPASS.- Redaction at the artifact and log boundary, before writing or printing.
- Never overstate replay. It reproduces inputs and harness behavior, not model determinism.
Layout
| Path | Role |
|---|---|
agentcheck/domain/ |
Contract models: scenarios, specs, runs, verdicts, findings. Fingerprinted and versioned. |
agentcheck/adapters/ |
The only layer allowed to import a framework SDK. |
agentcheck/inspect/ |
Import a target and extract an AgentSpec without running a turn. |
agentcheck/generate/ |
Derive, lint, select, and freeze suites. |
agentcheck/coverage/ |
Derived behavioral coverage over a spec and a scenario set. Pure contract analysis; imports no target. |
agentcheck/runner/ |
Orchestrator, worker, tool gateway, simulated world, budgets, network guard. |
agentcheck/evaluate/ |
Oracle evaluation and verdict assignment. |
agentcheck/replay/ |
Manifests, source binding, filesets. |
agentcheck/report/, agentcheck/baseline/, agentcheck/review/ |
Reporting, CI gating, human decisions on findings. |
agentcheck/regression/ |
Run-to-run behavioral comparison over stored artifacts. Executes nothing. |
agentcheck/gate.py |
The CI decision: runs the suite, compares the baseline, and answers whether a change blocks the build. Orchestrates the above; decides no verdicts of its own. |
agentcheck/identity.py |
Portable target identity and its bounded legacy compatibility path. |
agentcheck/redaction.py, agentcheck/privacy.py |
Credential redaction for artifacts and logs. |
agentcheck/cli.py |
The agentcheck command. |
spikes/environment_containment/ |
Repository-only, provider-neutral research contracts. Control metadata stays outside its minimal target leaves and never ships in distributions. |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 131 lines · 1,617 tokens per session scan A aad7113d5e40
AgentCheck AGENTS.md is an instructions file published in the GitHub repository WaseemGhanem98/AgentCheck (19 stars, last pushed today), licensed Apache-2.0. It adds 1,617 tokens to every session, about $0.0081 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
Doberman-Core AGENTS.md
AGENTS.md instructions for DobermanCore/Doberman-Core, covering claude.md — doberman operating manual, 0. on startup (every session), 1. what this repository is, 2. architecture & extension points and 3. prime directives (non-negotiable).
DM-Code-Agent AGENTS.md
Instructions for hwfengcs/DM-Code-Agent, covering agents.md, project intent, development rules, verification and important modules.
verbatim-citation-gate AGENTS.md
Instructions for tonydzi/verbatim-citation-gate, covering agents.md — working in this repo, what this repo is, stack and layout, how to verify a change and conventions.
node9-proxy CLAUDE.md
Claude Code instructions for node9-ai/node9-proxy, covering node9 proxy — claude code rules, pr checklist (required before every commit), test rules, code rules and architecture notes.
Hegelion CLAUDE.md
Instructions for Hmbown/Hegelion, covering claude.md, what is hegelion, build & development commands, install dependencies (uv recommended) and run all tests.
sieve CLAUDE.md
Instructions for SieveAI-dev/sieve, covering claude.md, 项目一句话, 项目状态, source of truth 层级 and 不可放宽的硬约束(十六条 / .cursorrules §二).