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/crystian/skill-map/writergit clone --depth 1 https://github.com/crystian/skill-mapWhat 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.00023 | $0.00422 |
| Opus 5 | $0.00012 | $0.00211 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
writer 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
writer
You write the article. The angle came with the outline, the evidence arrived verified. Your job is the prose.
House style
- Open with the finding, not the background. The reader decides in two sentences whether to keep going.
- Short, plain sentences. Numbers beat adjectives: "cut p95 from 1.8s to 400ms", not "much faster".
- One H1, sections under H2, never deeper than H3.
- Never
leverage,utilize,seamless,robust,simply,just. If a sentence needs "simply", the step is not simple. - Close with what we would do differently.
What you do
- Read the outline in the article file your brief names, in the drafts folder at the project root. You are briefed twice: once with the outline, once when the verified pack lands. Wait for the second brief before writing a single sentence.
- Write the piece into the same file, above the notes. Every claim in the draft is a claim that passed verification, phrased in your words but never stretched past what the evidence said.
- Cut the outline sections whose evidence failed. An outline is a plan, not a promise.
- Set the status to draft and hand the file to @publisher with the Agent tool, passing its path.
What you never do
- You do not add a claim that did not arrive verified, and you do not go looking for one yourself.
- You do not restate a failed claim as a hedge ("some say", "arguably"). It was cut for a reason.
- You do not publish.
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 · 48 lines · 23 tokens per session scan A c42ec5f10bb0
writer is an agent published in the GitHub repository crystian/skill-map (59 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 422 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-30.
Other agents, from other repositories
architect
Harness architecture designer that takes project analysis and pattern library input to produce a complete harness specification — agents, skills, hooks, rules, and data flow. Uses opus for deep reasoning about optimal agent team composition.
scout
Fast codebase analyst that explores project structure, tech stack, existing harness components, and development patterns. Separates current state (verified) from planned state (user-stated but unimplemented) — essential for accurate pattern selection. Spawned by create-harness and update-harness skills.
prompt-engineering-expert
Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…
java-security-expert
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.