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 kolodkin/devpowers --skill shortifygit clone --depth 1 https://github.com/kolodkin/devpowersWrote 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/kolodkin/devpowers/shortify)<a href="https://agentmods.dev/skills/kolodkin/devpowers/shortify"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/shortify/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/kolodkin/devpowers/shortify"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/shortify.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.00075 | $0.01105 |
| Opus 5.5 | $0.00030 | $0.00442 |
| Sonnet 5.5 | $0.00015 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
shortify 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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shortify
Apply as a review pass after writing or editing .md files in subdirectories, or manually via /shortify [file-or-glob].
Scope: Any .md file inside a subdirectory (e.g. docs/, src/), plus code comments and docstrings in source files.
Skip: CLAUDE.md, README.md, CHANGELOG.md, LICENSE.md, and any root-level .md files — these have their own conventions.
If the project has its own convention, follow it. This overrides every rule below.
Auto vs. manual:
- Markdown triggers automatically as a review pass after
.mdedits in subdirectories. - Code comments & docstrings are manual-only — never auto-triggered by a code edit. Run them on request:
/shortify <file-or-glob>on source files, or when the user opts in for the session ("apply shortify to my comments this session"), after which apply it as a review pass to code you edit for the rest of that session.
Checklist (markdown)
Apply in order:
1. Kill Redundancy — Link, Don't Restate
- Remove text and inline implementations that restate what code already shows. Link to the code instead.
- Link each doc–code pair once. By default the module docstring names its doc section, and the doc names a code path only when the reader must open it (an example file, a migration).
- A link names one module or package path:
See the storage/ package.No functions, classes, private helpers, line numbers or file lists — they go stale fast. - User guides: no implementation pointers. Code paths appear only inside prose that needs them.
- Design / architecture docs: optionally one module pointer under a heading.
- One example per concept. Delete duplicates. Keep short usage examples (3-5 lines); delete long inline code.
- API docs: call signature + one example, not internals.
- Merge overlapping sections — keep the clearer one.
2. Cut Wordiness
- Replace wordy phrases: "In order to" -> "To", "It is important to note that" -> delete, "This allows you to" -> delete or rephrase.
- Remove filler sentences that add no information.
- Prefer bullet lists over paragraphs for reference material.
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.
- 2d ago Changed · +17 lines 48ffc2e3cc6f
- 1mo ago First seen · 77 lines · 75 tokens per session scan A 5ce8584ebe25
shortify is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 1,105 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…