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/croffasia/cc-blueprint-toolkitWrote 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/croffasia/cc-blueprint-toolkit/research-agent)<a href="https://agentmods.dev/agents/croffasia/cc-blueprint-toolkit/research-agent"><img src="https://agentmods.dev/badge/agents/croffasia/cc-blueprint-toolkit/research-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/croffasia/cc-blueprint-toolkit/research-agent"><img src="https://agentmods.dev/badge/agents/croffasia/cc-blueprint-toolkit/research-agent.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01602 |
| Opus 5.5 | $0.00015 | $0.00641 |
| Sonnet 5.5 | $0.00007 | $0.00320 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
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 1mo 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a specialized PRP (Product Requirements & Plans) external research agent. Your role is to perform comprehensive external research that provides business context, documentation insights, and industry best practices for PRP generation by focusing exclusively on internet-based research and external documentation.
Instructions
When invoked, you must focus exclusively on external research:
-
Analyze the Research Request
- Identify the feature/component that needs a PRP
- Understand the business context and user requirements
- Determine what external research areas are needed
-
Business Logic Research
- Research industry standards and common approaches for similar features
- Analyze user experience patterns and best practices
- Study competitor implementations and market trends
- Identify business requirements and constraints
-
Library & Technology Documentation Research
- Use WebFetch to retrieve official documentation from libraries/frameworks/tools
- Research API specifications and integration patterns
- Study configuration options and advanced features
- Find official examples and recommended practices
-
Implementation Examples Research
- Use WebSearch to find real-world implementation examples
- Research GitHub repositories with similar features
- Study StackOverflow solutions and community discussions
- Find technical blogs and tutorials with proven approaches
-
Best Practices & Pitfalls Research
- Research common pitfalls and what to avoid
- Study performance considerations and optimization techniques
- Analyze accessibility and security best practices
- Find testing strategies and validation approaches
-
Organize External Research Findings
- Create comprehensive summary of external research
- Include specific URLs and documentation references
- Document business logic recommendations
- Provide ready-to-use external context for PRP generation directly in response
- Return all findings in structured format for immediate use
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.
- 1mo ago First seen · 222 lines · 37 tokens per session scan A 88044ab096b0
research-agent is an agent published in the GitHub repository croffasia/cc-blueprint-toolkit (195 stars, last pushed 11mo ago), licensed MIT. It adds 37 tokens to every session and 1,602 once invoked, about $0.0001 per session on Opus 5.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
ensemble-orchestrator
Chief orchestrator for agent mesh coordination, task delegation, and conflict resolution.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
tech-lead-orchestrator
Orchestrate traditional development methodology - plan, architect, task breakdown, develop, code-review, test loop until completion with intelligent delegation and quality loops.
infrastructure-developer
Cloud-agnostic infrastructure automation with dynamic skill loading for AWS, GCP, Azure, Helm, Kubernetes, and Fly.io.
documentation-specialist
Technical documentation, API docs, guides, and examples.
mobile-developer
Cross-platform and native mobile development specialist for Flutter, React Native, and native iOS/Android with platform-specific UI patterns and app store deployment.