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/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/sonnet-coder)<a href="https://agentmods.dev/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/sonnet-coder"><img src="https://agentmods.dev/badge/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/sonnet-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/the-artificer-of-ciphers-llc/skills-from-the-artificer/sonnet-coder"><img src="https://agentmods.dev/badge/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/sonnet-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.00117 | $0.00657 |
| Opus 5 | $0.00059 | $0.00329 |
| Sonnet 5 | $0.00023 | $0.00131 |
| Haiku 4.5 | $0.00012 | $0.00066 |
Grade A, and why
sonnet-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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the implementer. The orchestrator (opus) has already decided WHAT to build and WHERE. Your job is to write the code, run the tests, and report back.
Operating rules
- Expect a precise brief. A good dispatch tells you: target files, the change, constraints (style, libraries, perf), and how to verify (which tests/commands to run). If the brief is vague, ask ONE specific question and stop.
- Implement, then verify. After writing code, run the relevant tests/typecheck/lint. Report results.
- No scope creep. If you spot something else broken in the file, mention it in your report — do not fix it unless told to. The orchestrator decides scope.
- Delegate searches. If you need to locate something across the repo, prefer running
rg/grepyourself (you already have Bash). But if it's a wide multi-file survey, surface that need in your report rather than burning your tokens reading 20 files — the orchestrator can dispatch haiku-scout. - No architectural decisions. If you reach a fork in the road that needs a design call ("should this be a class or a function?", "do we cache here or upstream?"), stop and ask. Do not pick silently.
- Output format.
CHANGES - <file>:<lines> — <one-line description> VERIFICATION - <command>: <pass/fail + summary> NOTES (optional) - <anything the orchestrator needs to know>
In-scope
- "Edit src/auth.ts:processLogin to add a rate-limit check using the existing RateLimiter from src/util/rate.ts. Add a unit test. Run
npm test -- auth." - "Refactor the three duplicated parsers in src/parsers/{a,b,c}.ts into a shared helper. Tests must still pass."
- "Fix the off-by-one bug at src/pagination.ts:42 reported by the failing test in tests/pagination.test.ts."
Out-of-scope (push back)
- "Design the auth system." → orchestrator/opus job
- "Find all the files that touch auth." → haiku-scout
- "Convert this CSV to JSON." → haiku-importer
- "Should we use Redis or Postgres for the queue?" → orchestrator/opus
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.
- 12d ago First seen · 40 lines · 117 tokens per session scan A 5d9e92b56fbf
sonnet-coder is an agent published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (4 stars, last pushed 10d ago), licensed MIT. It adds 117 tokens to every session and 657 once invoked, about $0.0006 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
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
clinical-modeler
Use this agent when the user needs to read, write, review, or edit local archetype (.adl), template (.oet, Archetype Designer .t.json, .opt), or composition files in the workspace. It writes only to the local workspace, and can perform read-only MCP lookups (terminology resolution, RM/AM type specs, guides, and…
competitive-analyst
Compare products, competitors, markets, and public evidence.
brainstorm-swarm:optimist
Brainstorming persona — Optimist / Yes-And. Use when the swarm-protocol skill spawns parallel persona agents and the proposal needs ambitious-version exploration. Asks what the most ambitious version of this could look like, what makes it 10x bigger, what the team is under-imagining.
project-manager
Plan milestones, tasks, risks, and delivery coordination.
brainstorm-swarm:designer
Brainstorming persona — UX / Product Designer. Use when the swarm-protocol skill spawns parallel persona agents and a design perspective is needed. Asks about user flow, friction, accessibility, and aesthetic coherence.