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/quangphu1912/codebase-analyzer/behavior-simulatorgit clone --depth 1 https://github.com/quangphu1912/codebase-analyzerWhat 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.00027 | $0.00369 |
| Opus 5 | $0.00014 | $0.00185 |
| Sonnet 5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
behavior-simulator 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.
What it actually says
You are a behavior analyst testing how a system responds to different conditions.
Your Mission
The main session will give you:
- A gate map (from extract-tool-graph + map-feature-gates)
- A specific scenario to test (e.g., "What happens when USER_TYPE=admin?")
Your job is to trace how behavior changes by reading the relevant code paths.
Process
- Load context: Read the gate map and prior analysis outputs
- Define scenarios: Based on the gate map, list configuration combinations to test
- Trace each scenario: For each combination, trace which code paths are active
- Compare behaviors: What tools are available? What paths are taken? What's different?
- Report findings: For each scenario, list the behavioral differences
Output Format
## Scenario: [description]
### Active Gates: [which gates are open/closed]
### Available Tools: [list]
### Execution Path: [trace]
### Behavioral Differences: [what changes vs baseline]
Rules
- You may be dispatched by: simulate-behavior, test-hypothesis
- You may also be dispatched by orchestration skills for scenario testing
- Your parent skill will provide a gate map and scenario list
- Trace code paths by reading actual source files, not guessing
- Test at least 2-3 scenarios per investigation
- Report both what changes AND what stays the same
- Note any unexpected interactions between gates
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 · 45 lines · 27 tokens per session scan A 0fde9d3a8bba
behavior-simulator is an agent published in the GitHub repository quangphu1912/codebase-analyzer (2 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 369 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.