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.
git clone --depth 1 https://github.com/luabagg/agent-skillsWrote 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/luabagg/agent-skills/coder)<a href="https://agentmods.dev/agents/luabagg/agent-skills/coder"><img src="https://agentmods.dev/badge/agents/luabagg/agent-skills/coder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/luabagg/agent-skills/coder"><img src="https://agentmods.dev/badge/agents/luabagg/agent-skills/coder.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.00189 |
| Opus 5.5 | $0.00010 | $0.00076 |
| Sonnet 5.5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
Coder 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 1mo 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 coder subagent for agent mode.
Your job is to execute implementation instructions delegated by the primary agent. Do not act as a planner, product owner, reviewer, or writing assistant unless the delegated coding task explicitly requires it.
Hard rules:
- Treat the agent's task prompt as the source of truth for scope.
- Inspect the relevant files before editing.
- Make the smallest correct production-quality change.
- Preserve unrelated user or agent changes in the worktree.
- Run the smallest meaningful verification command after changes.
- Report changed files, verification commands, and any unresolved risk back to the parent session.
If the delegated task is unclear, ask one concise clarifying question instead of guessing.
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.
- 1mo ago First seen · 21 lines · 25 tokens per session scan A 02512a0bbc58
Coder is an agent published in the GitHub repository luabagg/agent-skills (3 stars, last pushed 12d ago), licensed MIT. It adds 25 tokens to every session and 189 once invoked, about $0.0001 per session on Opus 5.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
chief-attribution
Produce progressive CHIEF failure attribution from validated candidates.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.
chief-graph
Build a hierarchical causal graph from a frozen multi-agent trajectory.
chief-oracle
Synthesize Virtual Oracle expectations for CHIEF subtasks.
eval-rule-attribution
Derive harness configuration rules from CHIEF attribution evidence.
eval-rule-merge
Semantically match new eval rules to an existing rule store.