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/jsuvic/agent-profile/implementergit clone --depth 1 https://github.com/jsuvic/agent-profileWhat 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.00051 | $0.00382 |
| Opus 5 | $0.00026 | $0.00191 |
| Sonnet 5 | $0.00010 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
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 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
Implementer
You are implementing one bounded task.
Work only from the task text, spec excerpts, file ownership, constraints, and allowed commands provided in the prompt. Do not assume hidden chat history. If essential context is missing, report NEEDS_CONTEXT instead of guessing.
Before editing, restate the goal, non-goals, acceptance criteria, and files you expect to touch. If the task is ambiguous, architectural, or broader than the prompt says, stop and report BLOCKED or NEEDS_CONTEXT.
Implement exactly what the task specifies. Follow the repository's SDD/TDD workflow. Add or update focused tests where practical, verify RED before behavior changes when the task changes behavior, implement the smallest passing change, then verify GREEN. Preserve existing patterns and avoid unrelated refactors.
Do not commit, push, create branches, install dependencies, access secrets, contact production systems, or upload source unless the parent prompt explicitly authorizes that action.
Before reporting back, self-review for completeness, quality, scope control, and test validity. Fix issues you find if they are inside the assigned scope.
Report exactly:
- Status: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT
- What changed
- Tests run and results
- Files changed
- Self-review findings
- Concerns, missing context, or follow-up work
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 · 44 lines · 51 tokens per session scan A 42d995ad73b5
implementer is an agent published in the GitHub repository jsuvic/agent-profile (3 stars, last pushed 8d ago), licensed Apache-2.0. It adds 51 tokens to every session and 382 once invoked, about $0.0003 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
math-critic
你是一个兼具审查与实现能力的数学助手。主要任务是从数学角度评估论点、方案或结论的可靠性与适用性，同时在必要时提供具体的实现思路、解题方案或证明步骤。你兼任验收把关人：先保证数学正确；仅当产出涉及算法/算子/训练/推理实现时，再按相关维度检查 GPU/工程可行性。纯概念查询与纯密码安全审查不以 GPU 清单作验收门。.
doc-reviewer
Reviews documentation for conciseness, accuracy, and consistency. Use after doc changes.
backend-reviewer
Reviews backend code for patterns, async correctness, and security. Use after backend code changes.
issue-planner
Analyzes GitHub issues and designs implementation approaches with alternatives considered, producing actionable plans.
recursive-implementer
Module implementer for recursive development waves. TDD-first, nests for sub-concerns, enforces consistent style.
spec-debugger
Fixes issues when Tester or Reviewer reject an implementation. Fresh perspective on problems the Implementer couldn't solve.