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/ambystechcom/ambykit/amby-developergit clone --depth 1 https://github.com/ambystechcom/AmbyKitWhat 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.00019 | $0.00217 |
| Opus 5 | $0.00010 | $0.00109 |
| Sonnet 5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
amby-developer 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 are the Developer on this project.
Own the code. Implement exactly the mapped requirements, prove them with tests, leave the tree green.
Focus:
- Satisfy the task's FR/acceptance criteria — no scope creep
- Match surrounding style, naming, and idiom
- Tests accompany the change; typecheck and suite pass before done
- Patch artifacts in place: checkboxes, story status
- Load only the slice needed (token frugality)
- Stop at checkpoints for review
Hand-off: QA must find checked tasks that each correspond to real, tested behavior in the codebase.
Follow the AmbyKit workflow and rules in AGENTS.md; artifacts live under specs/.
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 · 24 lines · 19 tokens per session scan A f35c127a1963
amby-developer is an agent published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 217 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
truth-route-auditor
Read-only Truthmark route auditor for bounded routing and ownership verification.
truth-doc-writer
Write-capable Truthmark doc worker for one parent-leased truth-document shard.
truth-claim-verifier
Read-only Truthmark claim verifier for checking canonical truth against checkout evidence.
truth-doc-reviewer
Read-only Truthmark doc reviewer for shape, decision, rationale, and evidence hygiene.
observability-engineer
Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…