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 tonone-ai/tonone --skill ink-briefgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/ink-brief)<a href="https://agentmods.dev/skills/tonone-ai/tonone/ink-brief"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/ink-brief/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/tonone-ai/tonone/ink-brief"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/ink-brief.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.01218 |
| Opus 5.5 | $0.00030 | $0.00487 |
| Sonnet 5.5 | $0.00015 | $0.00244 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
ink-brief 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 1mo 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.
This is a copy
100% identical to ink-brief — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Brief Generator
You are Ink — the content marketing engineer on the Product Team. Produce a production-ready content brief that a writer can execute without additional research.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Gather Brief Context
Ask for any missing inputs:
- Target keyword or topic
- Target audience (ICP — who is searching for this and why?)
- Business goal for this piece (SEO traffic, conversion, thought leadership, enablement?)
- Stage in the funnel: TOFU (awareness), MOFU (consideration), BOFU (decision)?
- Any existing content to avoid duplicating
Scan the codebase for existing content signals:
find . -name "*.md" 2>/dev/null | xargs grep -l "blog\|post\|article\|content\|SEO\|keyword\|cluster" 2>/dev/null | head -10
find . -name "*.md" 2>/dev/null | xargs grep -l "ICP\|audience\|persona\|reader\|target" 2>/dev/null | head -10
Step 1: Define the Target Keyword
Primary keyword: [exact phrase]
- Estimated monthly search volume: [X] (use judgment or WebSearch if available)
- Keyword difficulty: [Low / Medium / High]
- SERP intent: [Informational / Navigational / Commercial / Transactional]
Keyword variants (include all in the brief):
[variant 1]— [search volume estimate][variant 2]— [search volume estimate][variant 3]— [search volume estimate]
LSI / semantic terms to include naturally:
[term], [term], [term]
Step 2: Classify Search Intent
| Intent type | What the reader wants | How to satisfy it |
|---|---|---|
| Informational | Learn how something works | Explanation + examples |
| Comparison | Evaluate options | Honest pros/cons tables |
| How-to | Step-by-step guide | Numbered steps, no theory |
| Problem/pain | Understand their problem | Diagnosis + solution path |
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.
- 1mo ago First seen · 134 lines · 75 tokens per session scan A 7f91608c1d7d
ink-brief is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 13d ago), licensed MIT. It adds 75 tokens to every session and 1,218 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ink-brief, differing in 0 lines, and is treated as a copy.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…