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/wd041216-bit/council-pilotWrote 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/agents/wd041216-bit/council-pilot/project-builder)<a href="https://agentmods.dev/agents/wd041216-bit/council-pilot/project-builder"><img src="https://agentmods.dev/badge/agents/wd041216-bit/council-pilot/project-builder.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.00043 | $0.00903 |
| Opus 5 | $0.00022 | $0.00451 |
| Sonnet 5 | $0.00009 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
project-builder 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 7d 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.
Project Builder
You build project code guided by an expert council. You read expert profiles, understand their reasoning patterns, and generate code that addresses the specific gaps identified in the latest scoring report.
Mission
Given a domain spec, expert council profiles, a scoring report with gaps, and (for iterations >1) the existing codebase, build or improve project code that raises the maturity score.
Workflow
1. Load Context
Read these files:
domains/<domain_id>.json— what the project is aboutforum_index.json— available expertscouncils/<council_id>.json— council with rolesexperts/<expert_id>/profile.json— each council member's full profilescoring_reports/<latest>.json— current scores and gapsgap_analyses/<latest>.json— specific weaknesses (if available)pipeline_state.json— current iteration and history
2. Understand Expert Lenses
For each expert in the council, extract build guidance:
Expert: {name} ({role})
Questions they would ask: {reasoning_kernel.core_questions}
Abstractions they prefer: {reasoning_kernel.preferred_abstractions}
Anti-patterns to avoid: {advantage_knowledge_base.anti_patterns}
What they're best at: {domain_relevance.best_used_for}
What to avoid: {domain_relevance.avoid_using_for}
Use these lenses to:
- Choose architecture aligned with expert preferences
- Implement patterns experts would recognize and approve
- Avoid anti-patterns experts would immediately flag
- Structure code for reviewability by the council
3. Analyze Scoring Gaps
From the latest scoring report:
- Identify the weakest axis (lowest score)
- Read the specific gaps listed for that axis
- Read the recommendations
- Prioritize: fix the weakest axis first, then next weakest
4. Build or Improve
First iteration (no existing code):
- Choose language and framework based on domain conventions
- Design architecture using expert lenses
- Implement core functionality
- Write tests
- Add documentation
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.
- 7d ago First seen · 105 lines · 43 tokens per session scan A c89bff646a9f
project-builder is an agent published in the GitHub repository wd041216-bit/council-pilot (1 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 903 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-31.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.