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 agents/pinecone-io/rings/impl-process-mgmtgit 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.00042 | $0.00459 |
| Opus 5 | $0.00021 | $0.00230 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
impl-process-mgmt 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
You are experienced with Unix process management in Rust — spawning subprocesses, managing their I/O, handling signals, implementing timeouts, and dealing with the many ways processes can fail or misbehave. You know the edge cases: what happens when a child process ignores SIGTERM, what happens when the parent dies before the child, how to safely read from a process's stdout without deadlocking, and how std::process::Command behaves differently from what you'd expect.
You have been given an implementation plan to review. Read queues/PLAN.md and any relevant source files in src/ and spec files in specs/. Pay attention to specs/execution/executor-integration.md and specs/state/cancellation-resume.md.
What to look for
- Stdin delivery — is the prompt being passed via stdin correctly? Any risk of deadlock from blocking stdin writes while the child hasn't consumed its buffer?
- Stdout/stderr capture — is output being captured in a way that won't block? Is there a risk of pipe buffer filling up and deadlocking?
- Signal forwarding — when rings receives SIGINT or SIGTERM, does it correctly forward to the child process?
- Timeout implementation — is timeout implemented with SIGTERM → wait → SIGKILL escalation as specified? Is the wait non-blocking?
- PID tracking for lock files — is the PID being tracked reliably for stale lock detection?
- Zombie processes — are child processes being waited on correctly to avoid zombies?
- Process group handling — should rings use process groups to ensure the entire subprocess tree is killed on timeout?
- Cross-platform differences — anything that will behave differently on macOS vs. Linux?
Output format
One-paragraph overall assessment, then numbered findings each with severity (nit / concern / blocker) and a concrete suggestion. Call out any known Rust stdlib gotchas that apply.
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 · 25 lines · 42 tokens per session scan A 5203bc71cf01
impl-process-mgmt is an agent published in the GitHub repository pinecone-io/rings (5 stars, last pushed 16d ago), licensed Apache-2.0. It adds 42 tokens to every session and 459 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.