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 jeremylongworth-source/AgentSkills --skill concise-technical-writinggit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/concise-technical-writing)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/concise-technical-writing"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/concise-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/jeremylongworth-source/agentskills/concise-technical-writing"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/concise-technical-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.00074 | $0.00375 |
| Opus 5 | $0.00037 | $0.00187 |
| Sonnet 5 | $0.00015 | $0.00075 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
concise-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 7d 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.
What it actually says
Concise Technical Writing
Core Workflow
- Identify audience, purpose, required facts, and action needed.
- Preserve technical accuracy; remove throat-clearing, filler, repetition, and vague praise.
- Lead with the change, decision, result, or ask.
- Use concrete nouns and verbs. Avoid inflated phrases.
- Keep structure proportional to the artifact: one-line commits, short PR summaries, scoped release notes, direct docs.
- Include risks, verification, and next steps only when useful.
Style Rules
- Prefer short sentences.
- Use active voice unless the actor is irrelevant.
- Replace abstract phrasing with specific behavior.
- Remove meta-commentary about why something is important.
- Avoid marketing language in engineering artifacts.
- Use bullets for scan-heavy details; use prose for short summaries.
Output Patterns
- Commit: imperative verb + object + qualifier.
- PR: summary, key changes, verification, risk.
- Changelog: user-visible change first.
- Status: done, blocked, next.
- Bug report: observed, expected, reproduction, impact, environment.
Deliverable Shape
For writing/editing work, provide:
- Final concise text first
- Optional brief rationale only when useful
- Preserved technical facts
- Removed ambiguity or verbosity called out only if requested
References
- Read
references/concise-writing-checklist.mdwhen editing technical text for clarity.
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.
- 7d ago First seen · 47 lines · 74 tokens per session scan A 898630c23762
concise-technical-writing is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 375 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-09-03.
Other skills, from other repositories
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
git-commit
A Git assistant for reviewing local changes and creating conventional commit messages, which are standardized summaries of code changes. It can also run Git hooks and push the commit.
git-workflow
A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
handoff
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.