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 furkangonel/cowrangler --skill copy-editorgit clone --depth 1 https://github.com/furkangonel/cowranglerWrote 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/furkangonel/cowrangler/copy-editor)<a href="https://agentmods.dev/skills/furkangonel/cowrangler/copy-editor"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/copy-editor.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.00620 |
| Opus 5 | $0.00010 | $0.00310 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
copy-editor 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 8d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copy Editor Skill
Goal
Transform rough or error-prone text into clean, fluent prose — fixing grammar, spelling, punctuation, and flow — while preserving the author's unique voice, terminology, and intent. Never rewrite so heavily that the result sounds like someone else.
Principles
- Voice preservation: Match the author's register (formal/casual, Turkish/English, technical/plain). Don't homogenize.
- Minimal intervention: Fix what's broken. Don't change what works. If a sentence is already good, leave it.
- Explain changes: After the edit, briefly note the most significant corrections (grammar rule, clarity issue, etc.) so the user learns.
- Preserve meaning: Never change meaning to improve style. Flag ambiguities instead of silently resolving them.
Steps
1. Assess the text
Read the full text before touching anything. Identify:
- Language (Turkish, English, mixed)
- Register (academic, casual, professional, technical)
- Recurring patterns vs. one-off errors
Success criteria: You understand the author's intent and voice before editing.
2. Edit in passes
Make two passes:
- Structural pass: Fix sentence fragments, run-ons, unclear pronoun references, paragraph flow
- Surface pass: Spelling, punctuation, subject-verb agreement, tense consistency, word choice
Success criteria: Output reads naturally at first read-through.
3. Deliver with annotations
Return the edited version in a code block or quoted block, then add a Changes section:
- List the 3–5 most important corrections with a one-line explanation each
- If you changed nothing (text was already clean), say so explicitly
Success criteria: User understands why each major change was made.
4. Offer alternatives (optional)
If a sentence could be fixed multiple ways, offer 2 options: the conservative fix and a more fluent rewrite. Let the user choose.
Why/Failure Modes
[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]
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.
- 8d ago First seen · 57 lines · 21 tokens per session scan A c449ad55d5eb
copy-editor is a skill published in the GitHub repository furkangonel/cowrangler (2 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 620 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
officecli-word-form
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document'…
officecli-data-dashboard
Use this skill to build a multi-element Excel dashboard — Dashboard sheet on open, multiple formula-driven KPI cards, multiple charts, sparklines, and conditional formatting — from CSV or tabular input. Trigger on: 'dashboard', 'KPI dashboard', 'analytics dashboard', 'executive dashboard', 'metrics dashboard', 'CSV to…
datamol
Pythonic wrapper around RDKit with simplified interface and sensible defaults. Preferred for standard drug discovery including SMILES parsing, standardization, descriptors, fingerprints, clustering, 3D conformers, parallel processing. Returns native rdkit.Chem.Mol objects. For advanced control or custom parameters…
clinicaltrials-database
Query ClinicalTrials.gov via API v2. Search trials by condition, drug, location, status, or phase. Retrieve trial details by NCT ID, export data, for clinical research and patient matching.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
esm
Comprehensive toolkit for protein language models including ESM3 (generative multimodal protein design across sequence, structure, and function) and ESM C (efficient protein embeddings and representations). Use this skill when working with protein sequences, structures, or function prediction; designing novel…