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 isvlasov/rageatc-oss --skill conducting-researchgit clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/conducting-research)<a href="https://agentmods.dev/skills/isvlasov/rageatc-oss/conducting-research"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/conducting-research/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/isvlasov/rageatc-oss/conducting-research"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/conducting-research.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.00038 | $0.00933 |
| Opus 5 | $0.00019 | $0.00466 |
| Sonnet 5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
conducting-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 12d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conducting Research
Guide systematic research: frame the question, find and judge sources, gather and synthesise, stop at the right point, present findings with confidence levels. This is process guidance, not domain expertise — findings are only as good as the sources available.
Skip when a single lookup or a straightforward answer from existing knowledge suffices.
Phase 1 — Define and frame
Before searching, establish (ask the user if unclear):
- Question — write it explicitly; break complex questions into 3–7 answerable sub-questions; note assumptions needing validation
- Scope — what's in and out, depth (overview vs deep dive), time constraints
- Purpose — what decision or action does this inform? This sets depth and output format
- Success criteria — what would make the research "complete enough"?
Phase 2 — Identify and evaluate sources
Aim for at least 3 high-quality sources before concluding anything.
Source hierarchy — start at the top, expand downward as needed:
- Primary — official documentation, research papers, primary data, project repositories and changelogs
- Secondary — established books and guides, expert blog posts (verify expertise), reputable analysis sites
- Community — Stack Overflow, Reddit/HN discussions, GitHub issues, conference talks — useful but verify
Judge each source on: authority (who wrote it; official or third-party), recency (still current? prioritise recent sources in fast-moving fields), accuracy (cites reliable sources; key claims verifiable elsewhere), bias (conflicts of interest; promotion disguised as neutral content), relevance (addresses the question in a context like yours).
Deprioritise sources with: no author attribution, promotional language, outdated information, no citations, claims conflicting with multiple reliable sources, or strong opinion without evidence.
By research type: technology evaluation — official docs first, then neutral benchmarks and production experience reports; concept understanding — authoritative introductions, cross-referencing multiple explanations; current events — sources from the last 6–12 months, verified across several; troubleshooting — official docs, then GitHub issues and dated Stack Overflow answers.
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.
- 12d ago First seen · 70 lines · 38 tokens per session scan A 38596d849acc
conducting-research is a skill published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 933 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-08-31.
Other skills, from other repositories
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
fusecore
Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.