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/Avyayalaya/agent-councilWrote 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/avyayalaya/agent-council/council-sweep)<a href="https://agentmods.dev/commands/avyayalaya/agent-council/council-sweep"><img src="https://agentmods.dev/badge/commands/avyayalaya/agent-council/council-sweep/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/avyayalaya/agent-council/council-sweep"><img src="https://agentmods.dev/badge/commands/avyayalaya/agent-council/council-sweep.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.00023 | $0.00352 |
| Opus 5 | $0.00012 | $0.00176 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
council-sweep 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 10d 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
Council Sweep
Daily-sweep mode of the Agent Council. Walks the paths declared in council.yaml#watch.paths and runs Council on every artifact modified in the time window.
Pre-conditions
- The
agent-councilPython package is installed. - A
council.yamlexists with awatch:block populated.
Invocation
Default window is 24 hours. If the user specifies a window (e.g., "the last 3 days"), pass it via --since:
python -m agent_council sweep --since=24h --config=council.yaml
python -m agent_council sweep --since=72h --config=council.yaml
If the user wants a one-off scan of a specific directory not in watch.paths, pass --root:
python -m agent_council sweep --since=24h --root=./drafts/ --config=council.yaml
Output
Print a summary table:
verdicts: SHIP=N · REVISE=N · HOLD=N · INCOMPLETE=N
log: council_log.jsonl (+N entries appended)
Then list each artifact + its verdict + one-line reason. Group by verdict (HOLD first, then REVISE, then SHIP) so the user sees blockers up front.
If the user asks "what changed since last sweep" or similar, suggest filtering by date/verdict using jq against council_log.jsonl.
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.
- 10d ago First seen · 41 lines · 23 tokens per session scan A 15e4a526c233
council-sweep is a command published in the GitHub repository Avyayalaya/agent-council (10 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 352 once invoked, about $0.0001 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 commands, from other repositories
review
A guided command for reviewing code changes by examining the current Git diff, the record of edits between versions. It checks quality, bugs, security, performance, and maintainability.
CLAUDE
Multi-agent collaboration platform for persistent, proactive AI agents across rooms, workspaces, skills, and external services.
cc-council
Comprehensive multi-agent council review with 6 protocols, 10 specialists, scoped scoring (per-scope thresholds and weights), state machine orchestration, auto-fix, and 50+ configuration flags.
speckit.critique.run
Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
deep-review
Multi-pass deep code review — security, quality, and test gaps.
agent
Create and manage custom AI agents.