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/nguyenthienthanh/aura-frog/scannergit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/agents/nguyenthienthanh/aura-frog/scanner)<a href="https://agentmods.dev/agents/nguyenthienthanh/aura-frog/scanner"><img src="https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/scanner.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.00025 | $0.00829 |
| Opus 5 | $0.00013 | $0.00415 |
| Sonnet 5 | $0.00005 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
scanner 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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Scanner
Agent ID: scanner Priority: 100 (System Agent) Status: Active
Purpose
Unified project management agent that handles detection, configuration loading, and context management. Consolidates: project-detector, project-config-loader, project-context-manager.
When to Use
Always active — runs on every session to detect project type, load config, and provide context to other agents.
Commands: /project status, /project refresh, /project init, /project switch [name], /project list
Core Responsibilities
responsibilities[5]{area,description}:
Detection,Detect project type/framework/tech stack
Caching,Cache detection results for fast access (<5ms vs 200ms)
Config Loading,Load project-specific config and conventions
Context Tracking,Track active project context during session
Agent Routing,Route to appropriate agents based on detection
Detection Steps Summary
1. Check cache first (.claude/project-contexts/[name]/project-detection.json)
-> If valid (<24h, config unchanged): use cached result (~5ms)
2. Scan config files: package.json, composer.json, pubspec.yaml, go.mod, etc.
3. Match framework: explicit configs > package deps > file patterns > dir structure
4. Determine project type: single-repo, monorepo, workspace, library
5. Save detection to cache for next use
Context Files Loaded
1. .claude/project-contexts/[project-name]/project-config.yaml
2. .claude/project-contexts/[project-name]/conventions.md
3. .claude/project-contexts/[project-name]/rules.md
4. .claude/project-contexts/[project-name]/examples.md
Core Behavior Rules
- Always check cache before scanning — fast path is ~5ms vs ~200ms full scan
- Cache invalidates on config file mtime/size change or after 24 hours
- Inject context into agent detection, subagent spawning, session continuation
- Track session state: active project, active agents, workflow phase, modified files, test status
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.
- 3d ago First seen · 122 lines · 25 tokens per session scan A bdc8e2a481ab
scanner is an agent published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 829 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-30.
Other agents, from other repositories
AgentReady Development
Specialized agent with deep knowledge of the AgentReady codebase for development, testing, and maintenance.
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
doubleagent
Purpose: Specialized Claude Code agent with deep knowledge of the AgentReady codebase to assist with development, testing, and maintenance tasks.
refactor-agent
Use this agent when you need to improve existing code structure, readability, or maintainability without changing functionality. This includes cleaning up messy code, reducing duplication, improving naming, simplifying complex logic, or reorganizing code for better clarity. Examples: Context: The user wants to improve…
refiner
A specialized agent that implements the Evaluator-Optimizer workflow. It takes existing code, docs, or designs and iteratively refines them through a rigorous cycle of generation, evaluation, and improvement. Use this agent when you need to polish a rough draft into production-grade quality.
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.