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 knack-run/knack-starter-pack --skill idea-clarifiergit clone --depth 1 https://github.com/knack-run/knack-starter-packWrote 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/knack-run/knack-starter-pack/idea-clarifier)<a href="https://agentmods.dev/skills/knack-run/knack-starter-pack/idea-clarifier"><img src="https://agentmods.dev/badge/skills/knack-run/knack-starter-pack/idea-clarifier.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.00123 | $0.02054 |
| Opus 5 | $0.00062 | $0.01027 |
| Sonnet 5 | $0.00025 | $0.00411 |
| Haiku 4.5 | $0.00012 | $0.00205 |
Grade A, and why
idea-clarifier 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Clarifier
Most idea-shaping conversations leave the user with a longer version of the same fog they walked in with. They produce vague audiences ("founders", "marketers"), pain points that are really categories ("inefficient workflows", "no time"), and next steps that read like a generic startup playbook ("build an MVP, talk to users, iterate"). This skill writes the opposite of that: a four-section artefact that names a specific audience, a pain in their language, an offer the user could put in front of them this week, and three to five ranked next actions. Five minutes of work. Usable.
When to use
- "I have an idea for a tool that helps consultants automate their proposals, what do I do with it?"
- "Help me think through this brief I've been kicking around for a Gmail extension."
- "I'm thinking about a newsletter for fractional COOs but I'm stuck on what to lead with."
- "I want to launch something this quarter but I don't know what."
Don't use this skill once the audience and pain are already clear and the user just wants execution help. Use it when the user is still in fog: an idea exists, but they can't yet name who it's for in one sentence and what's broken in their words.
Inputs the skill demands (in one round-trip, not four)
Ask the user for all of these in a single grouped question. If any are missing or vague, push back and ask again. Don't draft the four sections until every slot has a specific answer.
- The idea, in your own words: one paragraph, raw. Don't tidy it up first; the messiness contains signal.
- Who you think it's for, loosely: a job title, a situation, or a community. "Solo consultants who hate writing proposals" is fine; "small businesses" is not.
- What you've heard them complain about, in their words: quote a real conversation, a Reddit thread, a Slack message, a tweet. If you have nothing, say so honestly; the skill will route you to a different first action.
- One specific constraint: a budget cap, a deadline, a hard "I will not do X" (e.g. "no cold DMs", "no paid ads"). Be honest; the plan has to fit your real life.
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.
- 8d ago First seen · 98 lines · 123 tokens per session scan A bef23bfd8140
idea-clarifier is a skill published in the GitHub repository knack-run/knack-starter-pack (1 stars, last pushed 4mo ago), licensed MIT. It adds 123 tokens to every session and 2,054 once invoked, about $0.0006 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.