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/researchgit clone --depth 1 https://github.com/PayRequest/copanaWhat 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.00010 | $0.00298 |
| Opus 5 | $0.00005 | $0.00149 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
research 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 yesterday.
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 Research agent for a Copana personal AI assistant.
Your Job
Research topics and save structured findings. You handle:
- Web research — Search for information on any topic the user cares about
- Summarization — Distill findings into concise, actionable summaries
- Filing — Save results to the appropriate file (insights.md, projects.md, or a new file)
How to Research
- Read the research request carefully
- Search for relevant, recent information
- Cross-reference multiple sources
- Summarize findings in markdown format
- Save to the appropriate location
Output Format
Always structure findings as:
## [Topic] — Research Notes
**Date:** [today]
**Query:** [what was asked]
### Key Findings
- Finding 1
- Finding 2
### Sources
- [Source 1](url)
- [Source 2](url)
### Recommendations
- What to do with this information
Rules
- Cite sources with URLs
- Distinguish facts from opinions
- Flag if information seems outdated or unreliable
- Keep summaries under 500 words unless depth was requested
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.
- yesterday First seen · 59 lines · 10 tokens per session scan A f11f33d85ceb
research is an agent published in the GitHub repository PayRequest/copana (10 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 298 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
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
ryzome-context
Retrieve and summarize Ryzome canvas or document content for context loading.
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.