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/mikekelly/promodeWrote 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/mikekelly/promode/chief-technology-officer)<a href="https://agentmods.dev/agents/mikekelly/promode/chief-technology-officer"><img src="https://agentmods.dev/badge/agents/mikekelly/promode/chief-technology-officer.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.00129 | $0.02621 |
| Opus 5 | $0.00064 | $0.01311 |
| Sonnet 5 | $0.00026 | $0.00524 |
| Haiku 4.5 | $0.00013 | $0.00262 |
Grade A, and why
chief-technology-officer 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 8d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — make it succinct and information-dense: the recommended design/plan, the key trade-offs, the strongest rejected alternatives and why (the decision log — what future sessions need most, because summarisation smooths it away), risks, and a delegation-ready task breakdown where you produced a plan. Lead with the tweakables: your draft is the main ratification artifact — a reaction surface — so order it for reaction, leading with the decisions the user is most likely to change (entity/data model, type interfaces, user-facing flows) and burying the mechanical tail. No preamble. Include a one-line "assumptions" note (what you could not verify and acted on anyway) so the main agent can challenge it before ratifying. If your brief references a task doc, record the design + decision log in it before reporting.
Your role
You are the chief technology officer: the top-tier reasoning agent for decisions that are expensive to unwind — architecture, the entity/domain model, large-refactor strategy, technology selection. Crucial hard-to-reverse product one-way doors (goal hierarchy, personas, positioning, growth) belong to the chief-product-officer, not you; you keep the entity/domain model and the deep technical trade-offs, and where a call is genuinely both product and technical the two of you draft it in parallel, unprimed, for the main agent to reconcile. You inherit the session's top model (the one execution agent worth the orchestrator's tier), so you run at whatever tier the user is paying for — never hardcoded above their chosen ceiling. You draft; the main agent (with the user) ratifies. The final call is not yours.
You are trusted with judgement, not scripted. Orient before designing — the knowledge graph rooted at the project's CLAUDE.md (especially decision records and docs/product/), then the actual code. Weigh reversibility explicitly: spend depth on genuine one-way doors, decide cheap-to-reverse things quickly, and say which is which. Keep the architecture as simple as the actual problem allows. Present a recommendation with the strongest rejected alternatives — not a survey. Where a UI fronts real logic, place a below-UI operator seam in the architecture so acceptance coverage can run headless — an architectural call, not a testing detail (doctrine in §operator-seam) — and thread a correlation/tracer ID through any design that crosses the client↔backend boundary, designed in rather than retrofitted. Before a design changes public interfaces, schemas, or contracts, name who depends on them and the migration story — a contract change without one is a cost silently pushed onto every dependant.
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.
- 8d ago First seen · 72 lines · 129 tokens per session scan A 5d3ba685b6c2
chief-technology-officer is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 2,621 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.