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 agentmods add skills/boshu2/agentops/idea-genienpx skills add boshu2/agentops --skill idea-geniegit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/boshu2/agentops/idea-genie)<a href="https://agentmods.dev/skills/boshu2/agentops/idea-genie"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/idea-genie.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.00037 | $0.01195 |
| Opus 5 | $0.00018 | $0.00598 |
| Sonnet 5 | $0.00007 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
idea-genie 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 6d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Genie
One canonical root for idea work: elicit an evidence-grounded opportunity portfolio, or challenge a consequential idea with sealed independent perspectives. Both modes explore and advise; neither selects, schedules, tracks, implements, or validates work.
Modes
| Trigger phrases | Mode | Output contract |
|---|---|---|
| "idea genie", "what should we build", "supported opportunities" | elicit (single genie) | idea-portfolio.v1 via scripts/validate-output.sh |
| "challenge this idea", "compare independent proposals", "stress-test a one-way door" | duel (adversarial challenge) | idea-challenge.v1 via scripts/validate-challenge.sh |
Elicitation is the entry mode. Dueling is an optional escalation for a
consequential choice, typically consuming an idea-portfolio.v1 or a framed
question.
Elicit mode
Generate a small portfolio of evidenced options.
- State the question, constraints, non-goals, and sources. Hydrate only the sources this question needs and cite them; no merged context store.
- Separate cited observations from assumptions.
- Give each candidate its supporting evidence, overlap with existing capabilities, and one normal or edge scenario.
- Run a novelty pass, merge equivalents, and discard unsupported ideas.
- Stop when no materially new evidenced candidate appears.
- Write and validate
idea-portfolio.v1, then return it to the caller or Plan.
An empty no-new-work portfolio is valid. Plan alone may incorporate a selected
option into the existing bead or caller intent.
Duel mode
Produce independent challenges for a consequential choice. The result is advisory evidence for Plan. It never decides whether a plan is ready and never turns a later optional Premortem challenge into an approval gate.
Constraints
- Keep generation sealed until every perspective is complete to prevent later proposals from anchoring on earlier ones.
- Preserve dissent and concrete refutation attempts because Plan must see alternatives that synthesis might otherwise erase.
- Keep reversible choices lightweight because they do not warrant a pane manager, messaging service, council, or model-family rule.
- Emit no readiness, approval, quorum, retry, budget, helper, delivery, or tracker state because this strategy supplies evidence rather than lifecycle authority.
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.
- 6d ago First seen · 125 lines · 37 tokens per session scan A 656a284fbb69
idea-genie is a skill published in the GitHub repository boshu2/agentops (433 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,195 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-30.
Other skills, from other repositories
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.