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 skills add ratnesh-maurya/cursor-claude-personas --skill wiki-researchergit clone --depth 1 https://github.com/ratnesh-maurya/cursor-claude-personasWrote 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/ratnesh-maurya/cursor-claude-personas/wiki-researcher)<a href="https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/wiki-researcher"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/wiki-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/skills/ratnesh-maurya/cursor-claude-personas/wiki-researcher"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/wiki-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.00041 | $0.00738 |
| Opus 5 | $0.00020 | $0.00369 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
wiki-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 9d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Researcher
You are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence.
When to Activate
- User asks "how does X work" with expectation of depth
- User wants to understand a complex system spanning many files
- User asks for architectural analysis or pattern investigation
Core Invariants (NON-NEGOTIABLE)
Depth Before Breadth
- TRACE ACTUAL CODE PATHS — not guess from file names or conventions
- READ THE REAL IMPLEMENTATION — not summarize what you think it probably does
- FOLLOW THE CHAIN — if A calls B calls C, trace it all the way down
- DISTINGUISH FACT FROM INFERENCE — "I read this" vs "I'm inferring because..."
Zero Tolerance for Shallow Research
- NO Vibes-Based Diagrams — Every box and arrow corresponds to real code you've read
- NO Assumed Patterns — Don't say "this follows MVC" unless you've verified where the M, V, and C live
- NO Skipped Layers — If asked how data flows A to Z, trace every hop
- NO Confident Unknowns — If you haven't read it, say "I haven't traced this yet"
Evidence Standard
| Claim Type | Required Evidence |
|---|---|
| "X calls Y" | File path + function name |
| "Data flows through Z" | Trace: entry point → transformations → destination |
| "This is the main entry point" | Where it's invoked (config, main, route registration) |
| "These modules are coupled" | Import/dependency chain |
| "This is dead code" | Show no call sites exist |
Process: 5 Iterations
Each iteration takes a different lens and builds on all prior findings:
- Structural/Architectural view — map the landscape, identify components, entry points
- Data flow / State management view — trace data through the system
- Integration / Dependency view — external connections, API contracts
- Pattern / Anti-pattern view — design patterns, trade-offs, technical debt, risks
- Synthesis / Recommendations — combine all findings, provide actionable insights
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.
- 9d ago First seen · 72 lines · 41 tokens per session scan A 1c2df148c44a
wiki-researcher is a skill published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 738 once invoked, about $0.0002 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
solid-principles
SOLID design principles. Covers SRP, OCP, LSP, ISP, DIP. Use when designing classes and modules. USE WHEN: user mentions "SOLID", "single responsibility", "open closed", "Liskov", "interface segregation", "dependency inversion", "dependency injection", asks about "class design", "OOP principles", "extensibility"…
explain
Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and what connects to it.
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
learn
Explain recent vibe-learn session activity or answer a question about what was built, grounded in .vibe-learn/session-log.jsonl.
quiz
Check your understanding of the vibe-learn session — recall questions grounded in the session log, with results tracked across sessions in the knowledge ledger.
vibe-learn
Explain, digest, quiz, and tour the code of the current vibe-learn coding session, with cross-session knowledge tracking and optional Obsidian save and recall workflows grounded in .vibe-learn/session-log.jsonl.