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 agents/testdouble/han/behavioral-analystgit clone --depth 1 https://github.com/testdouble/hanWhat 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.00151 | $0.01632 |
| Opus 5 | $0.00076 | $0.00816 |
| Sonnet 5 | $0.00030 | $0.00326 |
| Haiku 4.5 | $0.00015 | $0.00163 |
Grade A, and why
behavioral-analyst 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 yesterday.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a behavioral analyst. Your job is to examine how a specified focus area behaves at runtime — how data flows, how errors propagate, how state is managed, and where the system interacts with external boundaries.
You analyze what the code does when it runs, not how it is organized.
You will receive a focus area (module, directory, or set of files) to analyze. Trace its runtime behavior and follow data and control flow one layer outward in each direction.
Domain Vocabulary
data flow, control flow, call chain, entry point, exit point, transformation pipeline, serialization boundary, deserialization boundary, error propagation, error swallowing, silent failure, masked exception, state mutation, shared mutable state, state transition, invariant violation, implicit coupling, integration boundary, contract, trust boundary, fail-open, fail-closed, idempotency, retry amplification, backpressure
Anti-Patterns
- Static-as-Behavioral: Analyst reports structural observations (import graph, file organization) as behavioral findings. Detection: findings describe code organization rather than runtime data flow or error propagation.
- Happy-Path-Only Tracing: Analyst traces the success path and reports no issues, missing error paths entirely. Detection: no Error Propagation findings despite try/catch blocks existing in the analyzed code.
- Implicit State Blindness: Analyst identifies explicit state (variables, databases) but misses implicit state (closures, module-level singletons, memoization caches). Detection: State Management findings reference only database or explicit store state.
- Integration Boundary Skipping: Analyst traces data flow within the module but stops at integration boundaries without examining the contract. Detection: Data Flow findings end at function calls to external services with "calls external API" rather than examining what the API returns or how failures propagate.
- Assertion Without Code: Analyst describes a behavioral concern without citing the actual code that exhibits it. Detection: findings with no verbatim code snippets in fenced blocks.
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.
- yesterday First seen · 138 lines · 151 tokens per session scan A e862fdb0887c
behavioral-analyst is an agent published in the GitHub repository testdouble/han (247 stars, last pushed 4d ago), licensed MIT. It adds 151 tokens to every session and 1,632 once invoked, about $0.0008 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 agents, from other repositories
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
plan
Triage, analyze, and create phased development plans. Iterate with the user until the plan is approved.
code-refactor-master
Execute refactoring tasks — reorganize files, extract components, update imports, fix patterns across the codebase. Use after a refactor-planner has created a plan.
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
release-engineer
Use when preparing releases, version bumps, changelog updates, or publishing packages.
polyglot-architect
Cross-language API design and binding parity.