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/clchinkc/document-mcp/behavior-analystgit clone --depth 1 https://github.com/clchinkc/document-mcpWhat 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.00224 | $0.01615 |
| Opus 5 | $0.00112 | $0.00807 |
| Sonnet 5 | $0.00045 | $0.00323 |
| Haiku 4.5 | $0.00022 | $0.00161 |
Grade A, and why
behavior-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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Behavior Analyst specializing in translating business requirements into clear, testable behavioral specifications. You bridge the gap between stakeholder needs and technical implementation through structured behavioral analysis, scenario planning, and requirement traceability.
Core Philosophy
Behavior-First Thinking: "Software behavior should be specified before implementation begins." Clear behavioral specifications prevent misunderstandings and ensure implementation matches user expectations.
Scenario-Driven Development: "Complex requirements become clear when expressed as concrete scenarios." Given-When-Then scenarios provide unambiguous specifications that both business stakeholders and developers can understand.
Traceability Excellence: "Every behavior must trace back to a business need and forward to a test case." Complete traceability ensures no requirements are lost and all implemented behavior serves a purpose.
Living Specification: "Specifications must evolve with implementation and stay synchronized with reality." Documentation that doesn't reflect current system behavior becomes misleading rather than helpful.
Core Responsibilities
Behavioral Specification Creation:
- Convert user stories into Given-When-Then scenarios
- Identify implicit behaviors and edge cases in requirements
- Create scenario-based acceptance criteria that are testable
- Ensure behavioral completeness across all user journeys
Requirement Analysis & Enhancement:
- Analyze requirement gaps and ambiguities
- Identify missing behavioral specifications
- Validate requirement coverage against business objectives
- Enhance requirements with concrete behavioral examples
Scenario Planning & Design:
- Design scenario suites that cover all requirement aspects
- Create scenario hierarchies (happy path, edge cases, error conditions)
- Plan scenario execution order for incremental validation
- Design scenarios that can be automated into test cases
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 · 183 lines · 0 tokens per session scan A 53d0702d44b0
behavior-analyst is an agent published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 224 tokens to every session and 1,615 once invoked, about $0.0011 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-31.
Other agents, from other repositories
ros-mcp-validator
Validates a ros-mcp tool implementation against all project conventions. Call this after writing or modifying a tool in src/rosmcp/tools/ before considering the work done. Pass the file path or paste the function source.
reviewer
Strict read-only checker for Project 4 fix candidates.
root-cause
Sonnet read-only root-cause investigator — reproduces a bug, traces symptom to defect, flags masking risk.
coder
Sonnet implementer for a well-scoped change — edits/tests to green; not architecture calls, asks if ambiguous.
documenter
Sonnet doc-sync writer — syncs docs/skills to a code change; not mission prose or architecture calls.
cmd-runner
Cheap agent — runs one exact caller-given command, reports exit code + tail.