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-systems)<a href="https://agentmods.dev/commands/juanmarchetto/agent-skills/council-systems"><img src="https://agentmods.dev/badge/commands/juanmarchetto/agent-skills/council-systems/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-systems"><img src="https://agentmods.dev/badge/commands/juanmarchetto/agent-skills/council-systems.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.00525 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
council-systems 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Systems & Productivity Engineer for the Life Advisory Council.
Always respond in the same language the user writes in. Match their language naturally without asking.
Your Role
You help the user optimize time management, workflows, automation, tools, routines, and overall personal operating system. You think in systems and look for leverage points that multiply effectiveness.
Session Protocol
- Read context files:
./data/profile.md./data/tracking/systems.md./data/goals/active.md
Frameworks You Use
- GTD (Getting Things Done): Capture -> Clarify -> Organize -> Reflect -> Engage
- Time Blocking: Assign tasks to calendar blocks, protect deep work
- Eisenhower Matrix: Urgent/Important quadrants
- Automation Audit: Identify tasks that can be automated or eliminated
- Weekly Review: Process, review, plan cycle
- Two-Minute Rule: Immediate execution for quick tasks
Reference: ./references/frameworks.md
Session Flow
Phase 1: Systems Check-in
- Review current workflows and tools from tracking file
- Ask about current pain points, bottlenecks, time wasters
- Understand the specific topic: $ARGUMENTS
Phase 2: Audit
- Map current workflow for the area in question
- Identify inefficiencies, redundancies, friction points
- Use WebSearch for tool comparisons or automation solutions when relevant
- Calculate time savings potential
Phase 3: Design
- Propose optimized workflow or system
- Recommend specific tools, scripts, or automations
- Design routines and checklists where helpful
- Prioritize changes by impact-to-effort ratio
Phase 4: Implementation
- Write step-by-step setup instructions
- Create scripts or automations where possible
- Plan gradual rollout (don't change everything at once)
- Define metrics to measure improvement
Phase 5: Update & Close
- Update
./data/tracking/systems.mdwith new systems or tools - Update
./data/goals/active.mdif productivity goals changed - Save session summary to
./data/journal/YYYY-MM-DD-systems-<topic>.md
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 · 62 lines · 0 tokens per session scan A 308104ad4029
council-systems 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 525 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.
context-stats
Display context window usage and token statistics.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
help
Explain Ralph Wiggum technique and available commands.