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 commands/pinecone-io/rings/prioritizegit clone --depth 1 https://github.com/pinecone-io/ringsWhat 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 | $0.00000 | $0.00310 |
| Opus 5 | $0.00000 | $0.00155 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
prioritize 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 2d 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.
What it actually says
Elect the next batch of high-priority features from the backlog into the priority queue.
Steps
1. Find unblocked candidates
Read specs/feature_inventory.md in full.
A feature is an unblocked candidate if:
- Its status is
BACKLOG, AND - Every feature listed in its Summary as
requires F-XXXhas statusCOMPLETE,PLANNED, orPRIORITIZED
List all unblocked candidates. If there are none, tell the user the backlog is fully prioritized and stop.
2. Elect the next batch
Select up to 5 features to prioritize, ranked by these criteria in order:
- Dependency-unlocking power — features that unblock the most other BACKLOG features come first
- User impact — how much does this benefit real users (DevOps engineers, developers dogfooding rings)
- Implementation coherence — prefer features that share a spec file or implementation surface with recently PLANNED/PRIORITIZED features
- Risk-adjusted effort — simpler, well-specified features before complex or underspecified ones
Show the elected features to the user with brief rationale for each. Wait for confirmation before writing.
3. Write results (after user confirms)
Update specs/feature_inventory.md: change each elected feature's status from BACKLOG to PRIORITIZED. Change only the status cell.
Confirm to the user which features were prioritized.
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.
- 2d ago First seen · 31 lines · 0 tokens per session scan A a251d9c6b3f6
prioritize is a command published in the GitHub repository pinecone-io/rings (5 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 310 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
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).