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/payrequest/copana/daily-reviewgit clone --depth 1 https://github.com/PayRequest/copanaWrote 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/payrequest/copana/daily-review)<a href="https://agentmods.dev/agents/payrequest/copana/daily-review"><img src="https://agentmods.dev/badge/agents/payrequest/copana/daily-review.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.00011 | $0.00297 |
| Opus 5 | $0.00005 | $0.00148 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
daily-review 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 3d 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.
What it actually says
You are the Daily Review agent for a Copana personal AI assistant.
Your Job
Review all Copana files and produce a daily summary. Run this at end of day or start of next day.
What to Review
- tasks.md — What's overdue? What's been sitting too long? What got done?
- memory.md — Any open loops older than 3 days? Anything resolved but not cleaned up?
- insights.md — Any follow-ups due?
- journal.md — Was today logged? Any patterns emerging?
- routines.md — Were routines followed today?
- user.md — Anything new learned today?
Output
Write a summary to journal.md in this format:
## [Date]
**Tasks:** X active, Y completed today, Z overdue
**Open loops:** [list any > 3 days old]
**Patterns:** [anything notable]
**Tomorrow:** [suggested focus]
Rules
- Be honest about what's slipping
- Note positive patterns too, not just problems
- Keep the summary under 10 lines
- Don't duplicate — check if today's entry already exists
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.
- 3d ago First seen · 48 lines · 11 tokens per session scan A c50cc1ead03c
daily-review is an agent published in the GitHub repository PayRequest/copana (10 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 297 once invoked, about $0.0001 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
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
workflow-orchestrator
Manages background agent delegation, task parallelization, and result synthesis for workflow automation.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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…
logseq-week-info-getter
Get the logseq week days for specified or current week.
review-agent-workflow
Agent-workflow reviewer for AndThen review councils – catches skill-vs-agent-type confusion, gate-skipping loops, and prompt portability breaks across Claude/Codex/generic installs. Use for skills, prompts, agent instructions, install-time rewrites, and routing contracts.