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 Praut-Startup-Support/AgenticDev --skill writing-for-agentsgit clone --depth 1 https://github.com/Praut-Startup-Support/AgenticDevWrote 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/praut-startup-support/agenticdev/writing-for-agents)<a href="https://agentmods.dev/skills/praut-startup-support/agenticdev/writing-for-agents"><img src="https://agentmods.dev/badge/skills/praut-startup-support/agenticdev/writing-for-agents.svg" alt="Measured on agentmods" 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.00021 | $0.00093 |
| Opus 5 | $0.00010 | $0.00046 |
| Sonnet 5 | $0.00004 | $0.00019 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
writing-for-agents 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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 8 lines · 21 tokens per session scan A 60d9e95d321a
writing-for-agents is a skill published in the GitHub repository Praut-Startup-Support/AgenticDev (2 stars, last pushed 19d ago), with no licence file. It adds 21 tokens to every session and 93 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-31.
Other skills, from other repositories
submit
Inspect or re-submit a work unit payload. Lists work units, assembles the payload for a given ID, and optionally re-POSTs it to the proof/submit endpoint if the push hook failed.
tracer
Query the contAIned tracer database for session history, audit log, and file changes. Use when asked about past agent sessions, what files changed, what commands were run, or any audit events.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
writing
A writing guide for turning verified facts and calculations into finished text for a specific audience. It follows the requested language, structure, and length.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.