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 skills/kryptobaseddev/cleo/ct-research-agentnpx skills add kryptobaseddev/cleo --skill ct-research-agentgit clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/skills/kryptobaseddev/cleo/ct-research-agent)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-research-agent"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-research-agent.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.00072 | $0.01817 |
| Opus 5 | $0.00036 | $0.00908 |
| Sonnet 5 | $0.00014 | $0.00363 |
| Haiku 4.5 | $0.00007 | $0.00182 |
Grade A, and why
ct-research-agent 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 2d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Context Injection
Protocol: @src/protocols/research.md Type: Context Injection (cleo-subagent) Version: 2.0.0
Purpose
Context injection for research and investigation tasks spawned via cleo-subagent. Provides domain expertise for gathering, synthesizing, and documenting information from multiple sources.
Capabilities
- Web Research - Search for current practices, standards, and solutions
- Documentation Lookup - Query official docs via Context7
- Codebase Analysis - Analyze existing code via grep/tools
- Synthesis - Combine findings into actionable recommendations
Parameters (Orchestrator-Provided)
| Parameter | Description | Required |
|---|---|---|
{{TOPIC}} |
Research subject | Yes |
{{TOPIC_SLUG}} |
URL-safe topic name | Yes |
{{RESEARCH_QUESTIONS}} |
Specific questions to answer | Yes |
{{RESEARCH_TITLE}} |
Human-readable title for output | Yes |
{{TASK_ID}} |
Current task identifier | Yes |
{{EPIC_ID}} |
Parent epic identifier | No |
{{SESSION_ID}} |
Session identifier | No |
{{DATE}} |
Current date (YYYY-MM-DD) | Yes |
{{TOPICS_JSON}} |
JSON array of categorization tags | Yes |
Task System Integration
@skills/_shared/task-system-integration.md
Execution Sequence
- Read task:
{{TASK_SHOW_CMD}} {{TASK_ID}} - Focus already set by orchestrator (skip if working standalone, set if needed)
- Conduct research (see Methodology below)
- Write output:
{{OUTPUT_DIR}}/{{DATE}}_{{TOPIC_SLUG}}.md - Append manifest:
{{MANIFEST_PATH}} - Complete task:
{{TASK_COMPLETE_CMD}} {{TASK_ID}} - Return summary message
Methodology
Research Sources
-
Web Search - Current practices, recent developments
- Use web search for up-to-date information
- Prioritize authoritative sources
-
Documentation Lookup - Official APIs, libraries
- Use Context7 for framework/library documentation
- Verify version compatibility
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 251 lines · 72 tokens per session scan A c41cded7c8b6
ct-research-agent is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 16d ago), licensed MIT. It adds 72 tokens to every session and 1,817 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…