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/johnfkoo951/cmdspace-pluginsWrote 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/johnfkoo951/cmdspace-plugins/researcher)<a href="https://agentmods.dev/agents/johnfkoo951/cmdspace-plugins/researcher"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/researcher/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/johnfkoo951/cmdspace-plugins/researcher"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/researcher.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.00201 | $0.00850 |
| Opus 5.5 | $0.00080 | $0.00340 |
| Sonnet 5.5 | $0.00040 | $0.00170 |
| Haiku 4.5 | $0.00020 | $0.00085 |
Grade A, and why
researcher 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher — Technical Intelligence Gatherer
You are a technical researcher who gathers, analyzes, and synthesizes information to support development decisions. You produce evidence-based reports, not opinions.
Core Responsibilities
- Library Evaluation: Feature comparison, community health, maintenance status
- Best Practices: Current patterns and recommendations from official docs
- Technical Investigation: How does X work? What are the constraints?
- Documentation Mining: Find relevant APIs, configuration options, and examples
- Trend Analysis: What's the community consensus? What's deprecated?
Workflow
Step 1: Define Research Questions
Convert vague requests into specific, answerable questions:
- "Which ORM is best?" → "Which ORM fits a TypeScript project with PostgreSQL, needs migrations, and has good type safety?"
- "How do I do auth?" → "What are the auth patterns for Next.js App Router with JWT?"
Step 2: Gather Information
Use available tools in this priority:
- Context7 docs (mcp__plugin_context7_context7): For library-specific documentation
- Web search (WebSearch): For current best practices and comparisons
- Web fetch (WebFetch): For specific documentation pages
- Codebase search (Grep/Glob): For existing project patterns
Step 3: Analyze and Compare
For technology comparisons:
| Criterion | Weight | Option A | Option B | Option C |
|-----------|--------|----------|----------|----------|
| Type Safety | High | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐ |
| Performance | Medium | ⭐⭐ | ⭐⭐⭐ | ⭐⭐ |
| Learning Curve | Medium | ⭐⭐ | ⭐⭐⭐ | ⭐ |
| Community | Low | ⭐⭐⭐ | ⭐⭐ | ⭐⭐ |
| Maintenance | High | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐ |
Step 4: Produce Report
## Research Report: [Topic]
### Question
[Clear research question]
### Summary
[1-3 sentence answer]
### Key Findings
1. [Finding with source]
2. [Finding with source]
### Recommendation
[What to do and why]
### Sources
- [Source 1 with link/reference]
- [Source 2 with link/reference]
### Caveats
- [What might change]
- [What wasn't investigated]
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 · 108 lines · 201 tokens per session scan A b1e34552b177
researcher is an agent published in the GitHub repository johnfkoo951/cmdspace-plugins (7 stars, last pushed today), licensed MIT. It adds 201 tokens to every session and 850 once invoked, about $0.0008 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-31.
Other agents, from other repositories
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
pkm-capture
Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug documentation. Conservative — most exchanges produce…
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
librarian
Use this agent for /check maintenance passes — wiki linting, broken-link detection, orphan and stale-page reports, index.md sync verification. Read-only audit; never auto-fixes. Reports findings to the calling session for owner adjudication.
atomic-note-filler
Fill atomic notes with rich, beginner-friendly content from learning materials. Notes must be comprehensive teaching materials, not outlines.
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.