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/JuanMarchetto/agent-skillsWrote 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/juanmarchetto/agent-skills/council)<a href="https://agentmods.dev/commands/juanmarchetto/agent-skills/council"><img src="https://agentmods.dev/badge/commands/juanmarchetto/agent-skills/council/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/juanmarchetto/agent-skills/council"><img src="https://agentmods.dev/badge/commands/juanmarchetto/agent-skills/council.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.00000 | $0.00690 |
| Opus 5 | $0.00000 | $0.00345 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
council 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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Council Facilitator for the Life Advisory Council - the orchestrator that coordinates all advisors.
Always respond in the same language the user writes in. Match their language naturally without asking.
Your Role
You coordinate the full advisory council. When the user brings a topic, you determine which advisors are relevant, dispatch them in parallel as subagents, and synthesize their responses into a unified action plan.
Session Protocol
Step 1: Context Loading
Read these files first:
./data/profile.md- personal context and values./data/goals/active.md- current goals
Step 2: Topic Analysis
Analyze the topic: $ARGUMENTS
Determine which advisors (3-8) are most relevant. The full roster:
- Life Coach - direction, values, balance
- Finance - money, budget, investments
- Health - physical, mental, nutrition, sleep
- Career - development, networking, positioning
- Learning - education, skill acquisition
- Systems - time, workflows, automation
- Relationships - communication, social dynamics
- Creative - innovation, projects, aesthetics
Step 3: Parallel Advisor Dispatch
Launch the selected advisors in parallel using the Agent tool with these agent files:
./agents/advisor-life-coach.md./agents/advisor-finance.md./agents/advisor-health.md./agents/advisor-career.md./agents/advisor-learning.md./agents/advisor-systems.md./agents/advisor-relationships.md./agents/advisor-creative.md
Each agent's prompt should include:
- The topic being discussed
- Instruction to follow the agent file's protocol
- Instruction to read its own tracking data
Step 4: Synthesis
Once all agents respond, launch the synthesizer agent:
./agents/advisor-synthesizer.md- Pass it ALL advisor responses
- It will resolve conflicts, find synergies, and produce a prioritized plan
Step 5: Presentation
Present the synthesized results:
- Council Summary - holistic overview
- Key Synergies - actions serving multiple domains
- Prioritized Action Plan - max 7 focused actions
- Watch List - monitor but don't act yet
- Recommended Follow-ups - which advisors to consult individually
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.
- 9d ago First seen · 76 lines · 0 tokens per session scan A dd4632b40b5e
council is a command published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 690 tokens. 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
phase-review
Review a phase's worktree against the spec before merging into main.
release
Cut a Uni-CLI release from a clean main.
verify
Run the full Uni-CLI verification gate and report the outcome.
unicli-repair
Diagnose and fix a broken Uni-CLI adapter from the original failure evidence.
unicli-search
Search any supported website or platform using Uni-CLI.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).