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 damianvtran/local-operator --skill writinggit clone --depth 1 https://github.com/damianvtran/local-operatorWrote 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/damianvtran/local-operator/writing)<a href="https://agentmods.dev/skills/damianvtran/local-operator/writing"><img src="https://agentmods.dev/badge/skills/damianvtran/local-operator/writing/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/damianvtran/local-operator/writing"><img src="https://agentmods.dev/badge/skills/damianvtran/local-operator/writing.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.00050 | $0.00580 |
| Opus 5.5 | $0.00020 | $0.00232 |
| Sonnet 5.5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
writing 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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing
The reader's time is the budget. Every sentence must change what the reader knows or does, or it goes.
AI tells to strip (scan for each)
- The em dash used as punctuation where a comma, colon, or full stop belongs.
- Filler openers: "It's important to note", "When it comes to", "It's worth mentioning".
- Hype adjectives: powerful, cutting-edge, world-class, effortless. Replace with the fact: a number, a capability, a limit.
- The "not just X, but Y" construction; the tacked-on tricolon ("fast, simple, and reliable") added for rhythm, not meaning.
- Journey, landscape, realm, delve, leverage, seamless, robust vocabulary.
- Hedge stacks: "might potentially be somewhat".
- Question hooks: "Ever wondered how ...?"
- Summary paragraphs that restate the introduction in new words.
- Uniform sentence lengths; every paragraph opening with a transition.
Rewrite patterns
| Disease | Fix |
|---|---|
| Passive with the actor dropped ("the decision was made") | Name the actor ("the team decided") |
| Nominalisation ("performed an analysis of") | Verb ("analysed") |
| Stacked clauses in one sentence | Split at the second clause |
| Generic claim ("improves performance") | A number or bounded statement ("cuts the page from 800ms to 90ms") |
| Opening with the topic's history | Open with the point |
| "not only X but also Y" | Say Y, or say X; pick one |
| Three items where two suffice | Two |
Structure
- First sentence states the point. A reader who stops after it must still have the gist.
- Headings are claims, not labels: "Deploys fail on dirty worktrees" beats "Deployment".
- One idea per paragraph; examples over abstractions; active voice by default.
Docs and posts
- Docs: what it is, why, then how. Commands and outputs verbatim; no placeholder prose the writer meant to replace.
- Posts: the title and hook must be true and specific; the piece delivers exactly what the hook promises. A platform cut keeps the argument only if the point sits in the first paragraph.
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.
- 5d ago First seen · 48 lines · 50 tokens per session scan A b9518df0f432
writing is a skill published in the GitHub repository damianvtran/local-operator (218 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 580 once invoked, about $0.0002 per session on Opus 5.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-10-11.
Other skills, from other repositories
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
prompt-engineering
Use when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is building-agents), NOT a standing CI eval…
coding-standards
Applies language-neutral engineering standards when writing or reviewing code, especially around boundaries, failures, domain models, dependencies, tests, and type safety.
domain-modeling
Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts. Use when clarifying terminology, bounded contexts, or durable design decisions.
setup-goal
Turns an idea into an approved goal package under ai-artifacts. Use when work needs clarified intent, scope, accepted facts, an implementation plan, and an explicit handoff.