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 6BNBN/FlowPilot --skill writing-skillsgit clone --depth 1 https://github.com/6BNBN/FlowPilotWrote 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/6bnbn/flowpilot/writing-skills)<a href="https://agentmods.dev/skills/6bnbn/flowpilot/writing-skills"><img src="https://agentmods.dev/badge/skills/6bnbn/flowpilot/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/6bnbn/flowpilot/writing-skills"><img src="https://agentmods.dev/badge/skills/6bnbn/flowpilot/writing-skills.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.00024 | $0.00642 |
| Opus 5 | $0.00012 | $0.00321 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Skills
Overview
Writing skills is TDD for process documentation: establish a failing baseline, write the minimum skill content that fixes the behavior, then refine it until the workflow is reliable.
Personal skills live in ~/.codex/skills.
Core Principle
If you did not observe a realistic failure mode before writing the skill, you do not yet know what the skill needs to prevent.
What a Skill Is
A skill is a reusable guide for patterns, tools, or workflows that future Codex sessions should be able to discover and apply.
Skills are:
- reusable workflows
- decision guides
- tool usage references
- proven implementation patterns
Skills are not:
- project-specific notes better suited for AGENTS.md
- narratives about one past debugging session
- mechanical rules better enforced by automation
Directory Structure
ext skills/ skill-name/ SKILL.md supporting-file.md
Use a flat namespace and keep supporting files only when the main file would otherwise become too heavy.
Required SKILL.md Frontmatter
- Only ame and description
ame uses letters, numbers, and hyphens only
- description starts with Use when...
- description explains when to load the skill, not the whole workflow
Discovery Optimization
Future Codex sessions need to find the skill quickly. Optimize for that by:
- Naming the trigger conditions clearly
- Putting the highest-signal symptoms in the description
- Using the same vocabulary users will naturally type
- Keeping the first screen concise and actionable
Authoring Workflow
RED
- Reproduce the failure mode without the skill
- Capture the rationalizations or mistakes that appear
GREEN
- Write the minimal skill content that closes those gaps
- Include only the steps, examples, and warnings needed to fix the observed failures
REFACTOR
- Test again under pressure
- Add explicit counters for any new loopholes
- Remove anything that does not help discovery or compliance
What ships with it
6 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 · 106 lines · 24 tokens per session scan A 8642789950bc
writing-skills is a skill published in the GitHub repository 6BNBN/FlowPilot (134 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 642 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 skills, from other repositories
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
Subagent Driven Development
Orchestrate specialized, autonomous AI agents to execute parallel subtasks with strict boundaries.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.