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 skills add yogirk/agent-council --skill agent-council-nudgegit clone --depth 1 https://github.com/yogirk/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/skills/yogirk/agent-council/agent-council-nudge)<a href="https://agentmods.dev/skills/yogirk/agent-council/agent-council-nudge"><img src="https://agentmods.dev/badge/skills/yogirk/agent-council/agent-council-nudge/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/skills/yogirk/agent-council/agent-council-nudge"><img src="https://agentmods.dev/badge/skills/yogirk/agent-council/agent-council-nudge.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.00048 | $0.01187 |
| Opus 5 | $0.00024 | $0.00593 |
| Sonnet 5 | $0.00010 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
agent-council-nudge 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 13d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble
# Read proactive config from ~/.council/config.json
_COUNCIL_PROACTIVE="true"
if [ -f "$HOME/.council/config.json" ]; then
_CP=$(cat "$HOME/.council/config.json" 2>/dev/null | grep -o '"proactive"[[:space:]]*:[[:space:]]*[a-z]*' | grep -o 'true\|false')
[ -n "$_CP" ] && _COUNCIL_PROACTIVE="$_CP"
fi
echo "COUNCIL_PROACTIVE: $_COUNCIL_PROACTIVE"
# Check for stale sessions (>7 days, no outcome recorded)
_STALE_SESSION="none"
_STALE_DAYS=""
if [ -d "$HOME/.council" ]; then
for _meta in $(find "$HOME/.council" -name "meta.json" -mtime +7 2>/dev/null | head -5); do
if ! grep -q '"outcome"' "$_meta" 2>/dev/null; then
_STALE_SESSION=$(basename "$(dirname "$_meta")")
_STALE_DAYS=$(( ( $(date +%s) - $(date -r "$_meta" +%s) ) / 86400 ))
break
fi
done
fi
echo "STALE_SESSION: $_STALE_SESSION"
[ "$_STALE_SESSION" != "none" ] && echo "STALE_DAYS: $_STALE_DAYS"
# Session nudge counter (max 2 per session)
_NUDGE_FILE="/tmp/council-nudges-$$"
_NUDGE_COUNT=$(cat "$_NUDGE_FILE" 2>/dev/null || echo "0")
echo "NUDGE_COUNT: $_NUDGE_COUNT"
Nudge Behavior
If COUNCIL_PROACTIVE is "false": do nothing. Do not suggest any council commands.
The user opted out.
If COUNCIL_PROACTIVE is "true" AND NUDGE_COUNT is less than 2:
You may suggest council commands at natural pause points in the conversation. The suggestion goes AFTER your full response, as a single quiet line. Never as a question. Never as the main content. Never mid-thought.
When to suggest /council
If the user's message matches ANY of these patterns:
- Explicit comparison: "should we use X or Y", "X vs Y", "which approach"
- Trade-off language: "trade-off", "pros and cons", "compare options"
- Architecture decisions: "how should we structure", "what pattern", "which database"
- Decision paralysis: "I'm not sure", "I'm torn", "what do you think about" + technical topic
- Multiple competing options being weighed
Suggest: Tip: Looks like a decision with trade-offs. /council gets 3 independent AI perspectives on this.
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.
- 13d ago First seen · 105 lines · 48 tokens per session scan A e4d466dbc05b
agent-council-nudge is a skill published in the GitHub repository yogirk/agent-council (89 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 1,187 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…