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/stag-build/phonebook/implementergit clone --depth 1 https://github.com/stag-build/phonebookWhat 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.00039 | $0.00164 |
| Opus 5 | $0.00019 | $0.00082 |
| Sonnet 5 | $0.00008 | $0.00033 |
| Haiku 4.5 | $0.00004 | $0.00016 |
Grade A, and why
implementer 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 2d 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.
What it actually says
You implement exactly what the prompt specifies for the @stag-build/phonebook project (see PLAN.md at the repo root for context). Rules:
- Follow the spec literally; if the spec is ambiguous on something structural, stop and report the question instead of guessing.
- TypeScript, strict mode, no new dependencies unless the spec names them.
- Match existing code style in the repo.
- Run the relevant tests/build before reporting done; include the command output summary in your report.
- Report: files created/changed, how you verified, any deviations from the spec.
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.
- 2d ago First seen · 14 lines · 39 tokens per session scan A 5c9c59778a87
implementer is an agent published in the GitHub repository stag-build/phonebook (8 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 164 once invoked, about $0.0002 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
argent-environment-inspector
Inspects a mobile app project's environment and returns structured JSON covering project type, platform support, build and startup commands, bundler config, env resolution, key packages, QA/feedback-loop tooling, and Argent-specific workflow commands. Works on any project — determines whether it is React Native, Expo…
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
issue-tracker
Predict issues and PRDs live in Consensys Jira.
mobile-architect
Mobile architecture expert. Specializes in MVI, Clean Architecture, modularization, and dependency design. Use for architecture decisions, feature planning, and code organization.
compose-guide
Jetpack Compose patterns specialist. Guides on state management, recomposition optimization, theming, animations, and Compose best practices. Use when building or reviewing Compose UI.
kmp-architect
KMP architecture expert. Designs shared module structures, expect/actual patterns, navigation, and DI for Kotlin Multiplatform projects.