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 JHostalek/dotclaude --skill intent-briefgit clone --depth 1 https://github.com/JHostalek/dotclaudeWrote 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/jhostalek/dotclaude/intent-brief)<a href="https://agentmods.dev/skills/jhostalek/dotclaude/intent-brief"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/intent-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/jhostalek/dotclaude/intent-brief"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/intent-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.00032 | $0.00266 |
| Opus 5.5 | $0.00013 | $0.00106 |
| Sonnet 5.5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
intent-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 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.
What it actually says
Elicit my intent with minimal interrogation; my attention is the scarce resource.
- Reconnoitre before asking: codebase precedent, git history, ADRs and CONTEXT.md, prior conversations, upstream docs, the web. Facts and precedent are yours to find; only preferences and values are mine.
- Present an assumption ledger. Default on two-way doors; management by exception, silence is consent.
- Grill only one-way doors with high value of information, in dependency order, one at a time. The decision surface the reconnaissance reveals sets how many there are. Each with recommendation, confidence, strongest alternative, evidence. Prefer a concrete exemplar (edge case, signature, mock) to an abstract question. Defer the rest to the last responsible moment.
- Run a brief pre-mortem.
- Stop when residual VOI is negligible. Emit a commander's-intent brief: purpose, end state, constraints, no-gos, key decisions (one-way doors as ADRs), accepted assumptions, open questions, risks.
Do not act until I confirm the brief.
What ships with it
1 file 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.
- 2d ago First seen · 16 lines · 32 tokens per session scan A c5275d02e37a
intent-brief is a skill published in the GitHub repository JHostalek/dotclaude (11 stars, last pushed 3d ago), licensed CC0-1.0. It adds 32 tokens to every session and 266 once invoked, about $0.0001 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-10-23.
Other skills, from other repositories
principle-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-mvp-scoper
Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
memstack-marketing-marketplace-submit
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.