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.
git clone --depth 1 https://github.com/indranilbanerjee/neels-pluginsWrote 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/indranilbanerjee/neels-plugins/client-review)<a href="https://agentmods.dev/commands/indranilbanerjee/neels-plugins/client-review"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/neels-plugins/client-review/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/indranilbanerjee/neels-plugins/client-review"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/neels-plugins/client-review.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.00026 | $0.00129 |
| Opus 5.5 | $0.00010 | $0.00052 |
| Sonnet 5.5 | $0.00005 | $0.00026 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
client-review 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 4d 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.
This is a copy
88% identical to client-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Client Review
Send internally-approved posts to the client for review.
Process
- Filter posts with status APPROVED_INTERNAL
- Build review package (gallery link or attached previews)
- Send via Slack (if connected) or email (if Gmail connected)
- Update status → PENDING_CLIENT for all sent posts
- Set reminder timer per approval-chain.json escalation rules
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.
- 4d ago First seen · 16 lines · 26 tokens per session scan A a5c7709ff6c7
client-review is a command published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 129 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to client-review, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
org-design
Assess organizational structure and recommend design improvements.
sites
Manage organic-os sites - add another website, switch the active site, or show registry status.
monday-report
Write a stakeholder-shareable weekly summary of what moved, shipped, and needs a decision.
task-board
Show the organic-os work queue and mirror it to Notion when available.
ma-strategy
Develop M&A strategy including target screening, synergy analysis, or integration planning.
finish-tasks
Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.