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 agentmods add skills/matthewdigiuseppe/mstack/title-shotgunnpx skills add matthewdigiuseppe/MStack --skill title-shotgungit clone --depth 1 https://github.com/matthewdigiuseppe/MStackWrote 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/matthewdigiuseppe/mstack/title-shotgun)<a href="https://agentmods.dev/skills/matthewdigiuseppe/mstack/title-shotgun"><img src="https://agentmods.dev/badge/skills/matthewdigiuseppe/mstack/title-shotgun.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.00062 | $0.00674 |
| Opus 5 | $0.00031 | $0.00337 |
| Sonnet 5 | $0.00012 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
title-shotgun 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 6d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mstack:title-shotgun
Stage: write Voice: writer
When to invoke
After /mstack:abstract-shotgun settles a framing. The title and abstract are read together by editors and search engines; pair them deliberately.
Procedure
-
Load.
paper/sections/abstract.tex,.mstack/config.yaml(target journals — different journals favor different title styles). -
Generate 8–12 candidates mixing forms:
Form Example Declarative "Trade Exposure Raises Protectionist Voting" Question "Does Trade Exposure Raise Protectionist Voting?" Colon construction (general:specific) "Threats to Trade: How Import Competition Reshapes Voting in Three Democracies" Anomaly framing "When the Losers Win: Compensation and Backlash in the Globalization Era" Mechanism framing "Compensation Without Trust: Why Aid to the Trade-Exposed Doesn't Move Votes" Quote framing "'Bring the Jobs Back': Industrial Decline and Electoral Realignment" Number-led "Three Decades of Trade Shocks and the New Politics of Protection" Single-noun-phrase "The Protectionist Turn" -
Score each candidate on three dimensions (1–5):
- Hook — would a reader stop scrolling?
- Precision — does the title accurately convey the claim?
- Searchability — would the right reader find this via a keyword search?
-
Filter. Drop any title with a 1 in any dimension. Compute
hook × precision × searchability. Surface the top 3. -
Recommend one. Tie hook-strength to the chosen abstract framing — a finding-first abstract pairs with a declarative title; a puzzle-first abstract pairs with a question or anomaly title.
-
Save options + scores + recommendation to
.mstack/title-shotgun-<YYYY-MM-DD>.md.
Outputs
.mstack/title-shotgun-<date>.md— candidates, scores, recommendation.- Summary block: top 3 with scores + recommendation.
Anti-patterns to refuse
- Clever-but-vague. A title that takes two readings to parse fails on hook + precision.
- Variables in the title. "Effect of X on Y in Z" is a placeholder, not a title.
- Sub-titles longer than titles. Reverse the colon if so.
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.
- 6d ago First seen · 64 lines · 62 tokens per session scan A 1be8a70e87c7
title-shotgun is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 9d ago), licensed MIT. It adds 62 tokens to every session and 674 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…