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 alexei-led/cc-thingz --skill writing-skillsgit clone --depth 1 https://github.com/alexei-led/cc-thingzWrote 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/alexei-led/cc-thingz/writing-skills)<a href="https://agentmods.dev/skills/alexei-led/cc-thingz/writing-skills"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/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/alexei-led/cc-thingz/writing-skills"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/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.00086 | $0.01279 |
| Opus 5 | $0.00043 | $0.00639 |
| Sonnet 5 | $0.00017 | $0.00256 |
| Haiku 4.5 | $0.00009 | $0.00128 |
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 11d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Skills
Create or reshape a skill so it triggers at the right time, stays lean, and matches this repo's source and build rules.
Read first
AGENTS.mdsection## Writing Agent/Skill Instructionsfor markdown signal rules.references/skill-principles.mdfor invocation, description, disclosure, split, and pruning rules.references/repo-conventions.mdforsrc/skills/, plugin manifests, overlays, generated outputs, and verification.src/skills/reviewing-instructions/references/scoring-rubric.mdonly after the draft exists and quality needs a final check.
Use this skill for
- creating a new skill
- rewriting a skill body or description
- splitting one skill into a skill plus references
- splitting one skill into two skills when the trigger or workflow boundary is real
- merging or extending overlapping skills after checking the neighboring skills
- pruning bloated skill prose, duplicate rules, or weak trigger phrasing
- adding target overlays or support files to a skill
Do not use this skill for
- scoring or linting prompt files without editing them; use
reviewing-instructions - broad agent, hook, extension, MCP, or package audits outside skill authoring;
use
evolving-config - ordinary docs, READMEs, or code comments; use
documenting-code - external library or API lookup; use
looking-up-docs - broad design debate before a concrete skill change exists; use
brainstorming-ideas
Workflow
- Find the source of truth under
src/skills/<name>/. Read the owningsrc/.agentbundler/packages/*.jsonand the closest neighboring skills before editing. Treatdist/as generated. - State the smallest correct shape:
- edit the current skill
- move conditional detail to
references/ - add a
.agentbundler/targets/<target>.jsonoverlay - split into two skills
- merge or fold into a neighboring skill
- Decide invocation mode and trigger surface.
- Model-invoked: use when the agent or another skill must discover it on its own.
- User-invoked: use when it is mostly a manual expert tool or reference.
- Keep one trigger per branch. Name real neighboring skills when overlap is possible. Put the NOT-clause in the description, not as an afterthought.
- Split content per the information hierarchy in
references/skill-principles.md. Keep only common-path rules in the main body. Move conditional detail toreferences/. Use Agent Bundler JSON overlays only when the base cannot stay vendor-neutral:frontmatterPatch,bodyPatch,files, anddeletedFiles. - Tighten wording until each line changes behavior. Delete generic agent advice, duplicated rules, and pretty prose.
- When adding or removing a public skill, update the owning package JSON in
src/.agentbundler/packages/. UpdateAGENTS.mdandREADME.mdwhen they expose the public skill surface or counts. - Before claiming done, run the narrowest verification that proves the new skill compiles and reads well.
- If quality is still uncertain, run
reviewing-instructionson the new or changed skill and apply the highest-value fixes.
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.
- 11d ago First seen · 163 lines · 86 tokens per session scan A ed50c4d3903e
writing-skills is a skill published in the GitHub repository alexei-led/cc-thingz (35 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,279 once invoked, about $0.0004 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
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
cognitive-doc-design
Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.