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 mamahoos/dot-files --skill idea-refinegit clone --depth 1 https://github.com/mamahoos/dot-filesWrote 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/mamahoos/dot-files/idea-refine)<a href="https://agentmods.dev/skills/mamahoos/dot-files/idea-refine"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/idea-refine/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/mamahoos/dot-files/idea-refine"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/idea-refine.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.02107 |
| Opus 5.5 | $0.00030 | $0.00843 |
| Sonnet 5.5 | $0.00015 | $0.00421 |
| Haiku 4.5 | $0.00007 | $0.00211 |
Grade A, and why
idea-refine 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 9d 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
98% identical to idea-refine — 3 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Refine
Overview
Refines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.
When to Use
- Use when an idea is still vague and needs shaping before it can become a plan
- Use when you need to stress-test assumptions before committing to a direction
- Use when you want to expand options before converging on one
- Trigger phrases: "Help me refine this idea", "Ideate on [concept]", "Stress-test my plan"
- Not for: a user who is unsure what they want at all (use
interview-me), or a direction already chosen that needs a spec (usespec-driven-development)
How It Works
- Understand & Expand (Divergent): Restate the idea, ask sharpening questions, and generate variations.
- Evaluate & Converge: Cluster ideas, stress-test them, and surface hidden assumptions.
- Sharpen & Ship: Produce a concrete markdown one-pager moving work forward.
Usage
This skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.
# Optional: Initialize the ideas directory
bash ~/.cursor/skills/idea-refine/scripts/idea-refine.sh
Output
The final output is a markdown one-pager saved to docs/ideas/[idea-name].md (after user confirmation), containing:
- Problem Statement
- Recommended Direction
- Key Assumptions
- MVP Scope
- Not Doing list
Detailed Instructions
You are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.
Philosophy
- Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.
- Start with the user experience, work backwards to technology.
- Say no to 1,000 things. Focus beats breadth.
- Challenge every assumption. "How it's usually done" is not a reason.
- Show people the future — don't just give them better horses.
- The parts you can't see should be as beautiful as the parts you can.
Process
What ships with it
4 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.
- 9d ago Changed · +15 lines 6a08d493df74
- 1mo ago First seen · 180 lines · 75 tokens per session scan A dd946a7a6653
idea-refine is a skill published in the GitHub repository mamahoos/dot-files (5 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 2,107 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to idea-refine, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
golang-style
Go conventions specific to this author. Use before writing or editing any Go (.go) file.
gh-cli
GitHub CLI (gh) conventions and the inline PR review recipe. Use when working with GitHub repositories, PRs, issues, actions, gh api, or any GitHub operations from the command line.
gh-pr
This skill should be used when creating a GitHub pull request via gh pr create. Covers the gh CLI mechanics; PR title and body conventions come from the pr-style skill.
plan-loop
Plan work with the user in a PLAN.md, then implement it step by step, with /clear once the context fills up. Use before creating a plan, when the user mentions a PLAN.md, or when resuming work after /clear.
astro-dso-doc
Bootstraps a deep-sky object (DSO) astrophotography project from raw acquisition frames (own rig, not a smart telescope), AND generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), and a ready-to-paste PixInsight project Description…
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…