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 skills add thiientv/godmode --skill writing-skillsgit clone --depth 1 https://github.com/thiientv/godmodeWrote 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/skills/thiientv/godmode/writing-skills)<a href="https://agentmods.dev/skills/thiientv/godmode/writing-skills"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/writing-skills/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/skills/thiientv/godmode/writing-skills"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/writing-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.00608 |
| Opus 5 | $0.00033 | $0.00304 |
| Sonnet 5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
writing-skills 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 9d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Skills
Write a skill for another agent to use under pressure. Context is a shared budget, so every paragraph must earn its place.
Design the boundary
- Collect concrete prompts that should and should not activate the skill.
- Name the responsibility in plain language and use a short verb-led name.
- Put all activation conditions in frontmatter
description; the body loads only after activation. - Keep
SKILL.mdprocedural and under 500 lines. - Move detailed rules, variants, schemas, and examples into one-level-deep
references/files. - Add a script only for deterministic repeated work, with
--helpand tests.
Use skill-checklist.md before opening a PR.
Write and test
- Use Agent Skills-compatible
nameanddescriptionfrontmatter. - State when to use, when not to use, safety boundaries, workflow, handoffs, and completion evidence.
- Avoid copying a reference repository's text, names, examples, or scripts; rewrite principles and record provenance.
- Add at least three positive and two negative routing cases, including close neighbors that must not activate.
- Create two or three realistic behavior cases with observable outputs and edge conditions before expanding the suite.
- Run each case in a fresh context with the candidate skill and with no skill or a frozen previous version. Keep prompts, fixtures, model settings, and output locations identical.
- Capture artifacts, public trace/tool summaries, duration, and usage. Grade deterministic assertions first and use blinded rubric or human review for judgment-heavy output.
- Optimize description triggering on a training set and choose the final result by a held-out validation set; do not paste missed query keywords into the description until fixtures pass by accident.
- Run the repository validator and at least one realistic forward test for a behavior-changing skill.
Descriptions should be specific enough to distinguish neighboring skills, but not so broad that every task activates the skill.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 65 lines · 66 tokens per session scan A 3f6df182eda1
writing-skills is a skill published in the GitHub repository thiientv/godmode (94 stars, last pushed 14d ago), licensed MIT. It adds 66 tokens to every session and 608 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-30.
Other skills, from other repositories
agent-evaluation-v2
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation-v3
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.