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 GuillemRoca/agent-skills-android --skill idea-refinegit clone --depth 1 https://github.com/GuillemRoca/agent-skills-androidWrote 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/guillemroca/agent-skills-android/idea-refine)<a href="https://agentmods.dev/skills/guillemroca/agent-skills-android/idea-refine"><img src="https://agentmods.dev/badge/skills/guillemroca/agent-skills-android/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/guillemroca/agent-skills-android/idea-refine"><img src="https://agentmods.dev/badge/skills/guillemroca/agent-skills-android/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.00041 | $0.00900 |
| Opus 5 | $0.00020 | $0.00450 |
| Sonnet 5 | $0.00008 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
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 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Refinement
Overview
Turn a vague idea into a focused, actionable direction. This skill uses structured divergent-convergent thinking: first expand possibilities, then evaluate and converge on the strongest direction, then sharpen into a one-pager ready for spec writing.
Philosophy: "Simplicity is the ultimate sophistication." Say no to 1,000 things to focus on the one that matters.
When to Use
- A feature request or product idea is unclear or overly broad
- You need to explore multiple directions before committing
- Stakeholders have different interpretations of "what we're building"
- Before writing a spec (feeds into
spec-driven-development)
Skip when: The requirement is already specific and unambiguous.
Core Process
Phase 1: Understand & Expand (Divergent)
-
Restate as "How Might We" — Convert the idea into an open question
- "Add offline support" → "How might we ensure users can accomplish core tasks without connectivity?"
-
Ask sharpening questions (answer or surface for human input):
- Who specifically benefits? (persona, not "users")
- What does success look like? (measurable outcome)
- What constraints exist? (timeline, tech debt, API limitations, minSdk)
- What has been tried before?
-
Generate 5–8 variations using these lenses:
- Inversion: What if we solved the opposite problem?
- Constraint removal: What if we had no legacy code / no backward compatibility?
- Simplification: What is the absolute minimum version?
- Combination: What if we merged this with another planned feature?
- Analogy: How do other Android apps solve this? (study Play Store top apps)
Phase 2: Evaluate & Converge
- Cluster into 2–3 directions — group related variations
- Stress-test each direction:
- Technical feasibility (existing modules, Android API levels, library support)
- User impact (who benefits, how much)
- Effort estimate (small / medium / large)
- Risk profile (what could go wrong)
- Surface hidden assumptions — list every assumption with a validation strategy
- "Assumption: Room migrations will handle schema changes → Validate: write migration test"
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 · 93 lines · 41 tokens per session scan A abb4049e455a
idea-refine is a skill published in the GitHub repository GuillemRoca/agent-skills-android (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 900 once invoked, about $0.0002 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
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
spk-doctrine-show-me
Explain Spec Kitty work with compact, checkable visuals. Use for specs, plans, architecture, control flow, diffs, status boards, or whenever prose obscures structure.
spk-admin-dashboard
Open or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views.