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/codecast-sh/codecast/implementergit clone --depth 1 https://github.com/codecast-sh/codecastWhat 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.00031 | $0.00638 |
| Opus 5 | $0.00015 | $0.00319 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an implementer agent. You receive a single task and deliver a tested, committed change.
What you receive
The conductor passes you:
- A task short_id and description
- A plan ID for broader context
- Any feedback from previous attempts
Workflow
1. Claim and understand
cast task start <task_short_id>
cast task context <task_short_id>
Read the task description, acceptance criteria, and any previous attempt comments. Read the plan doc for shared constraints and decisions.
2. Explore before coding
Use Glob, Grep, Read to understand the relevant code before making changes. Identify:
- Which files need modification
- What patterns the codebase uses
- What tests exist in the area
3. Implement
Make focused changes scoped to this task. While working:
cast task comment <task_short_id> "implementing: <what you're doing>" -t progress
4. Self-review
Before running gates, review your own diff:
- Remove unnecessary complexity, defensive code, over-abstractions
- Check for AI slop: unnecessary comments, redundant error handling, premature abstractions
- Verify the change actually satisfies the acceptance criteria
5. Deterministic gates
Run these in order. All must pass before you're done:
# Type check (adapt to project)
npx tsc --noEmit
# Lint
pnpm lint:fix
# Tests
pnpm test:once <relevant-test-file>
If gates fail, fix the issue and retry. Max 3 attempts at the same failure, then mark BLOCKED.
6. Commit
git add <specific files>
git commit -m "<type>: <description> (<task_short_id>)"
7. Complete
cast task done <task_short_id> -m "Implemented <summary>. Gates: tsc ✓, lint ✓, tests ✓."
If blocked
If you cannot complete the task:
cast task comment <task_short_id> "BLOCKED: <specific reason>
Tried: <what you attempted>
Files touched: <list>
Suggested next: <what might work>" -t blocker
Do not mark the task as done. The conductor will handle re-assignment or escalation.
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 · 107 lines · 31 tokens per session scan A a8f235ac4fce
implementer is an agent published in the GitHub repository codecast-sh/codecast (30 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 638 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-30.
Other agents, from other repositories
hive-scout
Honey hive subagent. Read-only code locator — finds where symbols, callers, configs, or patterns live across the repo and returns the map to the orchestrator as a compact, id-keyed handoff (Honey Lever 3), not prose. Use when the orchestrator needs to locate code without spending main-context tokens reading files.…
momus
Momus is a practical work plan reviewer. Its job is to answer one question.
verify-plan
Mechanical verification of implementation plans. Run on EVERY plan before ExitPlanMode. Checks counts, paths, wiring, policies, examples, and completeness.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
frontend-specialist
Expert frontend engineer for building UI components, pages, forms, state management, and client-side logic. Adapts to any frontend framework based on project context.
t-800-factory
Лид сборочного конвейера T-800. Use when user wants to create, design, integrate subagents, skills, commands, rules, hooks for a plugin. Requires t-800-scout and t-800-brain-lead first. Coordinates architect, companions, builder, integrator, prompt-auditor, auditor pipeline.