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 isvlasov/rageatc-oss --skill ideatinggit clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/ideating)<a href="https://agentmods.dev/skills/isvlasov/rageatc-oss/ideating"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/ideating.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.00910 |
| Opus 5 | $0.00018 | $0.00455 |
| Sonnet 5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
ideating 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideating
Three activities with very different footprints: quick capture (zero friction), dialogue-driven ideation (expand thinking), and idea review (decide what to pursue). Match the activity to what the user brings — and keep capture frictionless above all.
Skip this skill when the user already knows what they want (understanding-the-ask) or is evaluating a specific solution (solutioning).
Activity 1 — Quick capture
The user has a thought and wants it preserved before it vanishes.
- Accept whatever is given — a phrase, a sentence, a question.
- Append to the project's
ideas.mdwith the date and a one-line summary (format below). - Confirm saved, move on.
No forced formality: if the user says "quick idea: versioned skills", write exactly that. Don't expand, structure, or ask clarifying questions unless the user wants dialogue.
Activity 2 — Dialogue-driven ideation
Frame the exploration first — "What are we exploring? Starting fresh, or building on something?" A rough focus is enough; it doesn't need to be a problem statement.
Pick facilitation techniques to fit, and use them naturally without naming them ("What if we looked at this from a purely emotional perspective?", not "Now we're using Red Hat thinking"):
- Expansive exploration — SCAMPER prompts (substitute? combine? adapt?), analogies from other domains, random connections
- Perspective-shifting — Six Thinking Hats lenses, stakeholder viewpoints, "How might we" questions
- Assumption-surfacing — "What are we assuming must be true?", reverse an assumption and explore what becomes possible
Your highest value is introducing new dimensions, not elaborating what's already there:
- "What domain completely unrelated to this solves a similar challenge?"
- "What would someone with opposite expertise notice that we're missing?"
- "What becomes possible if we reverse [key constraint]?"
Keep divergence and convergence separate, and signal transitions explicitly: "we're generating possibilities now — no evaluation yet" → "let's shift to the critical lens". Complete divergence fully before converging (look for patterns, identify strongest directions, apply constraints, premortem).
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 · 71 lines · 37 tokens per session scan A 5bd3dacb1f67
ideating is a skill published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 910 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
commit-optimization
Use when configuring settings.json to reduce fuse-commit-pro's context token usage.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
time-of-day
Discover when you are most active and most productive with Claude Code by bucketing sessions and events into hour-of-day and day-of-week bins from their timestamps, then flagging peak versus low-output windows. Uses the session list, per-session events, and analytics daily trends. Use when planning a schedule or…