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 agentmods add instructions/appleweiping/weiping_council/agents-mdgit clone --depth 1 https://github.com/appleweiping/WEIPING_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/instructions/appleweiping/weiping_council/agents-md)<a href="https://agentmods.dev/instructions/appleweiping/weiping_council/agents-md"><img src="https://agentmods.dev/badge/instructions/appleweiping/weiping_council/agents-md.svg" alt="Measured on agentmods" 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.00575 | $0.00575 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
WEIPING_COUNCIL AGENTS.md 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 6d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WEIPING_COUNCIL Agent Instructions
WEIPING_COUNCIL is an honest multi-model deliberation runtime. It preserves protocols, model routing evidence, dissent, timings, degraded-state warnings, and session artifacts so users can inspect what happened.
Source Of Truth
Read README.md, CLAUDE.md, pyproject.toml, .codex/skills/weiping-council/SKILL.md, backend/runtime.py, backend/providers/router.py, backend/council/orchestrator.py, backend/main.py, and vc.py before non-trivial work. The project skill is mandatory for implementation, release, maintenance, monitoring, or upgrade tasks.
Boundaries
- Never fake model success or hide degraded provider/memory state.
- Provider credentials must stay environment-only and redacted from API, CLI, UI, logs, and docs.
- Keep provider identity separate from council-member identity.
- Tests must be hermetic; do not let ambient machine credentials decide test results.
- Do not revive retired local mailbox/state or markdown memory dependencies.
- Preserve
vipin-councilas a compatibility alias only where historically needed.
WEIPING Constellation
WEIPING_WIKI is the public durable route map, not a runtime dependency. WEIPING_LAB is the broader research workbench. Council may export inspectable session JSON for Lab, but Council must not require Lab workspace state, private .env, local DBs, caches, or active Lab services to run.
Recurring WEIPING maintenance may inspect entry evidence, health/status commands, docs, and git state. It should not edit saved sessions, runtime outputs, local provider config, frontend build artifacts, or generated files unless the user explicitly scopes Council work.
Saved handoffs live at data/sessions/<uuid>.json. Treat that as runtime evidence with a schema contract, not as source to stage during general maintenance. Required fields include id, query, protocol, created_at, stages, final_answer, confidence, dissent, audit_trail, routing, metrics, provider_health, model_call_traces, degraded, and warnings.
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.
- 6d ago First seen · 42 lines · 575 tokens per session scan A bb5e1727ba98
WEIPING_COUNCIL AGENTS.md is an instructions file published in the GitHub repository appleweiping/WEIPING_COUNCIL (136 stars, last pushed 8d ago), licensed MIT. It adds 575 tokens to every session, about $0.0029 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).