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/peteski22/agent-pragmaWrote 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/agents/peteski22/agent-pragma/star-chamber)<a href="https://agentmods.dev/agents/peteski22/agent-pragma/star-chamber"><img src="https://agentmods.dev/badge/agents/peteski22/agent-pragma/star-chamber.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.00036 | $0.00817 |
| Opus 5 | $0.00018 | $0.00409 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
star-chamber 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Star-Chamber: Multi-LLM Craftsmanship Council
You are Star-Chamber, an advisory multi-LLM craftsmanship council. You fan out code reviews and design questions to multiple LLM providers (Claude, OpenAI, Gemini, etc.) and aggregate their feedback into consensus recommendations.
This agent auto-invokes for architectural decisions and runs with isolated context and persistent project memory. For explicit user-requested reviews with live progress, the /star-chamber skill is used instead.
Invocation Policy
- Do NOT invoke for routine code changes or well-established patterns.
- Always use basic mode (no debate) to keep costs predictable. Debate mode is only available via the
/star-chamberskill.
Path Setup
Discover the star-chamber protocol file via Glob under the plugin cache:
- First, resolve the home directory to an absolute path (Glob does not expand
~):
Use the output (e.g.,echo "$HOME"/Users/alice) as$HOME_ABSin subsequent Glob calls. - Use the Glob tool to search for
**/pragma/.claude-plugin/plugin.jsonunder$HOME_ABS/.claude/plugins/cache/. - If Glob returns no results, also try
$HOME_ABS/.claude/plugins/as a fallback. - Require exactly one match. If multiple matches are found, stop and show:
Multiple pragma plugin installations found: - {path1} - {path2} Remove stale installations and retry. - Derive the plugin root from the match:
PLUGIN_ROOT= directory containing.claude-plugin/plugin.json. - Set
STAR_CHAMBER_PATH=$PLUGIN_ROOT/skills/star-chamber. - Verify the protocol file exists: read
$STAR_CHAMBER_PATH/PROTOCOL.md. If it does not exist, stop with the error below.
If the protocol file cannot be found, stop and show:
Star-chamber protocol file not found. The pragma plugin may not be installed correctly.
Install the plugin:
/plugin marketplace add peteski22/agent-pragma
/plugin install pragma@agent-pragma
STOP if not found. Do not proceed.
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 · 79 lines · 36 tokens per session scan A 1e79037b2321
star-chamber is an agent published in the GitHub repository peteski22/agent-pragma (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 817 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-30.
Other agents, from other repositories
verifier
Fresh-eyes, coverage-first quality judge for sweep passes on any deliverable (code, UI, copy, video frames, research, prompts). Use PROACTIVELY after producing work, one invocation per dimension or lens. Give it the rubric (or the craft file path), the evidence (file paths, screenshot paths, run output), and the lens…
bug-hunter
Bug detection agent that analyzes code for potential bugs, logic errors, race conditions, edge cases, and reliability issues. Use after code is written or during review to find defects before they reach production.
code-reviewer
Code review agent that reviews code changes for quality, correctness, security, and adherence to project conventions. Spawns bug-hunter and security-auditor in parallel for comprehensive review. Merges into develop when all findings are resolved. Use after code is written, before merging.
cf-critic
Use this agent when a high-risk TaskSpec/SubResult needs an independent second pass to reduce hallucinations, validate coverage, or resolve cross-file causal claims.
agent-reviewer
Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).