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 himanshufound/council --skill council-litegit clone --depth 1 https://github.com/himanshufound/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/himanshufound/council/council-lite)<a href="https://agentmods.dev/skills/himanshufound/council/council-lite"><img src="https://agentmods.dev/badge/skills/himanshufound/council/council-lite/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/himanshufound/council/council-lite"><img src="https://agentmods.dev/badge/skills/himanshufound/council/council-lite.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.00114 | $0.01068 |
| Opus 5 | $0.00057 | $0.00534 |
| Sonnet 5 | $0.00023 | $0.00214 |
| Haiku 4.5 | $0.00011 | $0.00107 |
Grade A, and why
council-lite 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 12d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council Lite — Multi-Approach Orchestrator (claude.ai)
Run one request through several skills or approaches, then aggregate: one merged answer, or the single best. This is the claude.ai version of Council.
How it differs from the full Claude Code skill — say this plainly if it matters to the user: claude.ai runs everything in a single conversation with no subagents, no shell, and no way to auto-discover your other installed skills. So Council Lite cannot give each skill a truly separate, walled-off run. Instead it does the best a single context allows: each pass is produced as independently as possible, deliberately not leaning on the earlier passes. If the user needs real isolation (each skill blind to the others), point them to the full Council skill in Claude Code. Do not overstate the isolation here.
When to run
- The user invokes
/council//council-lite, or - asks in plain language to compare approaches / run several skills / get multiple takes and combine them. In the natural-language case, confirm once ("Want me to run this through a few approaches and combine them?") before starting — don't silently produce six drafts.
If the request itself isn't stated yet, ask for it before running.
Step 1 — Choose what to run it through
There is no filesystem discovery here, so ask the user directly. Offer two ways, as a short conversational prompt (no special picker UI exists — use a plain numbered list and let them reply in text):
- Named skills — if the user has other skills uploaded to claude.ai, they name the ones to include (e.g. "run it through my minimalist-ui and web-design-guidelines skills"). For each named skill, apply that skill's own instructions during its pass.
- Ad-hoc lenses — if they don't have matching skills, have them name distinct approaches/personas/lenses instead (e.g. "a security reviewer, a performance reviewer, and a plain-English explainer"). Each becomes one pass.
Confirm the resolved list in one line before running. There is no persistent skillset store in this version — selections are per-conversation. If the user wants saved, reusable skillsets, that's a full-Council (Claude Code) feature; say so rather than pretending to save one.
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.
- 12d ago First seen · 102 lines · 114 tokens per session scan A 301cff963c27
council-lite is a skill published in the GitHub repository himanshufound/council (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 114 tokens to every session and 1,068 once invoked, about $0.0006 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 skills, from other repositories
skillci-guardrails
Use this skill whenever you create, edit, or review a Claude Skill — any SKILL.md file, or the eval cases/config next to one. Most SKILL.md files today are written or edited by an agent, not typed by hand, so this closes the loop by having the agent that just wrote the skill also author it defensively and verify it…
example-skill
Writes a single changelog entry summarizing a code change, given a short description of what changed.
clean-skill
A skill with no lint issues, used as a starting point for the lint-on-type test.
skill-with-referenced-issue
Has a clean SKILL.md but an unsafe referenced script.
configuration
A guide to configuring OpenClaw, including its main YAML configuration file, environment variables, performance settings, and security options.
ci-cd
A skill for configuring continuous integration and continuous delivery, or CI/CD: automated steps that build, test, and sometimes package or publish software when code changes. It includes examples for Jenkins, GitLab CI, and GitHub Actions.