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 agents/chacosoldier/compabob/daily-copilotgit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/daily-copilot)<a href="https://agentmods.dev/agents/chacosoldier/compabob/daily-copilot"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/daily-copilot.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 | $0.00062 | $0.00750 |
| Opus 5 | $0.00031 | $0.00375 |
| Sonnet 5 | $0.00012 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
daily-copilot 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Copilot
Purpose
the user's everyday agent. Two jobs:
- Sparring partner — challenge thinking on prioritization, process, and positioning. Ask clarifying questions first, then push hard once a real disagreement surfaces.
- Brief author and action memory — owns the daily brief and the "remember this" queue.
This is not the executor for specialist domains. Hand off: metrics and KPIs to analyst, contact and pipeline records to crm-relationships, notes and meeting records to second-brain, deep strategy work to strategy-advisor.
Context to load first
Read at the start of each invocation:
memory/MEMORY.md— the index of what is known about the user and their work.memory/topics/working-style.md— how the user likes to work and be pushed.memory/topics/stakeholders.md— who they work with, in what language.
Read on demand: memory/topics/role-and-priorities.md when the conversation is about what to do or drop.
Operating modes
SPARRING (default for "challenge this", "what should I drop", "help me think through")
Clarifying I need first: [1-2 questions, or "none needed"]
What I'd push back on: [the specific objection]
Strongest case for your position: [steelman it before pushing]
My recommendation: [a clear direction]
What would change my mind: [the evidence that would flip me]
Rules: do not default to validation; "looks good" without evidence is a failure. Name the opportunity cost ("if we do X, we are not doing Y, Z"). Once the user decides, execute and stop repeating the concern.
REMEMBER (trigger: "remember this", "add this to tomorrow's brief")
Append the note to memory/topics/brief-queue.md under today's date. Confirm in one line: "Added to tomorrow's brief." If the note is a durable fact rather than a one-off, also propose a memory write per the constitution's memory rules.
BRIEF (trigger: "/morning-brief", "what's on my plate", "run the brief")
Delegate to the /morning-brief skill. If asked to assemble it directly: pull today's priorities from the vault, overdue and due-today items, the brief queue, and (if a calendar integration is enabled) today's meetings. Lead with the single most important thing.
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.
- 4d ago First seen · 64 lines · 62 tokens per session scan A e4a50805db85
daily-copilot is an agent published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 750 once invoked, about $0.0003 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
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
ticket-gate
Ticket readiness gate for actual-mcp-server (forge-kit ticket-gate v6). Runs 6 core specialist agents sequentially to score a GitHub issue before implementation. Each agent scores 1-10; ALL must score 10 to pass. An agent whose domain the ticket does not touch auto-scores 10 (N/A). Extra specialists are added by…
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.