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 nimadorostkar/Claude-Skills-collection --skill editinggit clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collectionWrote 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/nimadorostkar/claude-skills-collection/editing)<a href="https://agentmods.dev/skills/nimadorostkar/claude-skills-collection/editing"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/editing/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/nimadorostkar/claude-skills-collection/editing"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/editing.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.00034 | $0.01226 |
| Opus 5 | $0.00017 | $0.00613 |
| Sonnet 5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
editing 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editing
Purpose
Make writing shorter and stronger without making it yours. Most editing is cutting; most weak prose is not badly constructed but merely padded.
When to Use
- Editing your own draft.
- Editing someone else's writing.
- Prose that is technically correct and somehow limp.
- Cutting a piece to a length.
Capabilities
- Structural editing: order, emphasis, what to cut entirely.
- Line editing: sentence-level force and clarity.
- Identifying the specific constructions that weaken prose.
- Preserving another author's voice.
Inputs
- The draft, and what it is meant to do.
- The audience.
- The constraint: a length, a level, a tone.
Outputs
- A shorter, clearer version.
- Structural notes distinguished from line edits.
- The author's voice intact.
Workflow
- Structure before sentences — There is no point polishing a paragraph you are about to cut. Read for the argument first: does each section earn its place, and are they in the right order?
- Cut the throat-clearing — Most drafts genuinely begin in the second or third paragraph. Find where the piece actually starts and delete everything above it.
- Then edit the lines — Cut hedges, filter phrases, and nominalizations. Prefer the active voice unless the passive is doing real work.
- Read it aloud — Every sentence you stumble over is a sentence that needs rewriting. This is the single most reliable line-editing tool there is.
- When editing someone else's work, separate suggestion from correction — A grammatical error is a correction. A different word choice is a suggestion, and it is theirs to decline.
Best Practices
- The first draft is 30% too long. This is nearly universal and the cut nearly always improves it.
- Hedging destroys force: "it could be argued that", "in some sense", "arguably", "perhaps", "somewhat". Assert or do not.
- Filter phrases put distance between the reader and the point: "it is important to note that", "there is a growing body of evidence suggesting that". Delete the filter and state the thing.
- Nominalizations bury the verb: "made a decision" is "decided"; "performed an analysis of" is "analyzed"; "is indicative of" is "indicates".
- The passive voice is not a sin, but it is usually evasion: "mistakes were made" exists to avoid saying who made them.
- Never rewrite another author's voice into your own. Fix what is broken; leave what is merely different.
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 · 119 lines · 34 tokens per session scan A cb2f9d40dbbd
editing is a skill published in the GitHub repository nimadorostkar/Claude-Skills-collection (26 stars, last pushed 25d ago), licensed MIT. It adds 34 tokens to every session and 1,226 once invoked, about $0.0002 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
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".