Borrowing it
Nothing to install: this file belongs to pinecone-io/rings. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pinecone-io/rings/main/.claude/commands/process-ideas.mdgit clone --depth 1 https://github.com/pinecone-io/ringsWrote 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/commands/pinecone-io/rings/process-ideas)<a href="https://agentmods.dev/commands/pinecone-io/rings/process-ideas"><img src="https://agentmods.dev/badge/commands/pinecone-io/rings/process-ideas/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/commands/pinecone-io/rings/process-ideas"><img src="https://agentmods.dev/badge/commands/pinecone-io/rings/process-ideas.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.00000 | $0.00926 |
| Opus 5.5 | $0.00000 | $0.00370 |
| Sonnet 5.5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
process-ideas 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 2mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read rough ideas from queues/IDEAS.md, evaluate them against the existing specs, run them through the full review panel in parallel, then produce concrete spec proposals or new feature entries.
Steps
1. Load context
- If
queues/IDEAS.mddoes not exist at the project root, tell the user to create one with their rough notes and stop. - Read
queues/IDEAS.mdin full. - Read
specs/feature_inventory.mdto understand what is already specified. - Read
specs/index.mdand any spec files directly relevant to the ideas. - Read
specs/overview.mdandspecs/mvp.mdto understand design principles and scope.
2. Classify each idea
For each idea in queues/IDEAS.md, classify it as:
- Already covered — essentially described by an existing spec; note the F-NNN number(s) and explain how.
- Extension — adds nuance or a new option to an existing feature; identify the F-NNN being extended.
- New feature — genuinely not covered; note which spec file it would belong in.
- Out of scope / conflict — conflicts with a design principle; explain why and suggest an alternative if one exists.
Set aside anything classified as "already covered" or "out of scope" — do not send those to the review panel.
3. Dispatch review panel in parallel
For all ideas classified as extension or new feature, launch ALL of the following agents simultaneously using the Agent tool. Give each the same task:
"You are a member of the rings project review panel. Before reviewing, orient yourself by reading:
specs/index.md— what rings is and core conceptsspecs/overview.md— design principles and target userspecs/mvp.md— what was built first and whyspecs/feature_inventory.md— what is already specified
Review the following proposed ideas and provide your perspective from your area of expertise. For each idea, identify concerns, risks, gaps, or improvements before we commit to writing them into the spec. Also note anything the idea is missing that your area of expertise would require.
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.
- 2mo ago First seen · 82 lines · 0 tokens per session scan A 9676a57a42e6
process-ideas is a command published in the GitHub repository pinecone-io/rings (6 stars, last pushed 25d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 926 tokens. 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 commands, from other repositories
cwb
Control coding-with-beat (play / pause / skip / now-playing / music source / like / mode / search / list). Use $ARGUMENTS as a free-form intent.
cwb-classical
A music-search helper for classical pieces featuring piano, strings, orchestras, and composers such as Bach and Mozart.
cwb-chinese
A music-search helper for Chinese music, including traditional styles, Mandarin-language songs, folk music, and instruments such as guzheng, guqin, and erhu.
cwb-focus
A music-search helper for quiet instrumental audio used for concentration and deep work.
cwb-hype
A music-search helper for energetic morning, workout, and motivational tracks.
cwb-jazz
A music command for finding jazz, bossa nova, and relaxed café-style tracks. It runs three searches and displays the results in separate groups without starting playback.