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 onehorizonai/skills --skill one-initiative-briefgit clone --depth 1 https://github.com/onehorizonai/skillsWrote 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/onehorizonai/skills/one-initiative-brief)<a href="https://agentmods.dev/skills/onehorizonai/skills/one-initiative-brief"><img src="https://agentmods.dev/badge/skills/onehorizonai/skills/one-initiative-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/onehorizonai/skills/one-initiative-brief"><img src="https://agentmods.dev/badge/skills/onehorizonai/skills/one-initiative-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.00050 | $0.02061 |
| Opus 5 | $0.00025 | $0.01030 |
| Sonnet 5 | $0.00010 | $0.00412 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
one-initiative-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 12d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initiative Brief
Turn a rough roadmap idea into a clear initiative brief, then create it or finalize an existing draft.
Core rule
- Understand the problem before proposing solutions; produce a design doc, not code
- Decide mode early and keep it stable:
new initiative→ flow ends in createexisting initiative draft→ flow ends in finalize/update, not create
- Write in markdown; use tables or Mermaid only when they clarify the design
- Preserve existing media in canonical markdown exactly (
,[video](url#one-video=1),[youtube](url#one-youtube=1),[figma](url#one-figma=1)) — do not remove, replace, or normalize unless the user asks - Edit existing descriptions with
patch-document+ initiativetaskId; useupdate-initiativefor metadata only - Product perspective only — not implementation, engineering tasks, or estimates
- Default to feature-level scoping unless the user describes broader product/company work
- Business goals are supporting context, not the backbone
- Acceptance criteria: observable, user-verifiable ("user can do X on Y screen")
- Name user-facing surfaces in feature sections
- Out-of-scope items need a short reason so boundaries hold without chat context
Boundaries
Use when:
- shaping roadmap-first planned work
- initiative needs background, scope, non-goals, risk, or rollout clarity
- user needs a brief others can review and execute from
Do not use when:
- brief is complete and user only wants the record created
- request is a bug, ongoing work, or Todo
- user wants a status update, not a new brief
Other skills:
one-create-task— initiative already clear enough to create directlyone-task-management— operational lookup, assignment, tagging outside this flowone-initiative-summary— reporting on existing initiatives
Metadata
- Pull taxonomy before creation when product, customer, company, goal, or component signals exist
- Prefer product labels first; attach goals, components, company/customer labels on high-confidence matches only
list-taxonomyonly after scope is stable- Multiple plausible labels → ask, don't guess
- Clear parent roadmap effort → set
parentInitiativeId - Owner/parent in structured metadata — not
Owner:lines in markdown unless requested - Related work → URLs or markdown links, not plain text labels
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 214 lines · 50 tokens per session scan A 4236422e4021
one-initiative-brief is a skill published in the GitHub repository onehorizonai/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 2,061 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-31.
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…