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 monkilabs/opencastle --skill technical-writinggit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/technical-writing)<a href="https://agentmods.dev/skills/monkilabs/opencastle/technical-writing"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/technical-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/monkilabs/opencastle/technical-writing"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/technical-writing.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.00054 | $0.01645 |
| Opus 5 | $0.00027 | $0.00822 |
| Sonnet 5 | $0.00011 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
technical-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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writing
The goal is writing a tired engineer understands on the first read. Four layers get you there, one question each: what kind of document is this, how do sentences address the reader, how much does each sentence carry, and can any sentence be read two ways. Apply all four, then run the unslop skill over the result.
Three rules sit above the layers:
- Cut every word that does no work. "In order to" is "to". "It is important to note that" is nothing.
- Use the short, everyday word. "Use", not "utilize". A long word has to buy its length with precision.
- When a rule makes a sentence worse, fix it another way or leave it alone. A sentence that follows every rule and sounds machine written has failed.
The codebase is the word list. Write the real symbol, file, flag, or command name, never a synonym or a description of it. Do not invent jargon; use the words a developer says out loud.
Layer 1: pick the mode (Diataxis)
One document, one mode. Two questions pick it: does the content inform action or understanding, and does it serve learning or work?
| Learning | Work | |
|---|---|---|
| Action | Tutorial | How-to |
| Understanding | Explanation | Reference |
- Tutorial. You are the teacher and the learner's success is your job. Open with what they will build, not what they will "learn". Every step produces a visible result, and you say what they should see. Cut explanation to one clause and a link. Write as "we", in commands.
- How-to. Solve a problem a person has, not an operation the machine can perform. Assume competence, skip teaching, allow forks: "If you want x, do y." Name it by the task.
- Reference. Describe, only describe. No instruction, no opinion, no hedging. State facts, options, limits, and errors. Mirror the structure of the thing described. Generate from code where possible so it stays true.
- Explanation. One bounded topic, readable away from the product. Each title should tolerate an implicit "About...". Give design decisions, history, constraints, alternatives. Opinion is allowed here and nowhere else.
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 · 92 lines · 54 tokens per session scan A 246124ae48bc
technical-writing is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 11d ago), licensed MIT. It adds 54 tokens to every session and 1,645 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-09-03.
Other skills, from other repositories
product-architect
Complete product development system with 80 agents and 36 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
cursor-prompting
Internal guidance for composing cursor-agent prompts and picking models for coding, review, diagnosis, and research tasks inside the Cursor Claude Code plugin.
cursor-result-handling
Internal guidance for presenting Cursor helper output back to the user.
goal-runner
Use when the user asks to advance, continue, or work on the project's long-horizon goal (or to set one up) — the policy for goal-driven increments driven through the goal companion, one increment at a time, delegated via the codex/cursor delegation skills, honestly recorded.
agentflow
Expert guidance for building, debugging, and extending applications with AgentFlow (10xscale-agentflow). TRIGGER when: code imports from agentflow (e.g. from agentflow import, StateGraph, Agent, ToolNode, AgentState); user references agentflow.json or CLI commands (agentflow init, agentflow api, agentflow play…
agentflow
Expert guidance for building, debugging, and extending applications with AgentFlow (10xscale-agentflow). TRIGGER when: code imports from agentflow (e.g. from agentflow import, StateGraph, Agent, ToolNode, AgentState); user references agentflow.json or CLI commands (agentflow init, agentflow api, agentflow play…