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 sergeyklay/.agents --skill research-itgit clone --depth 1 https://github.com/sergeyklay/.agentsWrote 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/sergeyklay/.agents/research-it)<a href="https://agentmods.dev/skills/sergeyklay/.agents/research-it"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/research-it/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/sergeyklay/.agents/research-it"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/research-it.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.00155 | $0.03197 |
| Opus 5 | $0.00077 | $0.01598 |
| Sonnet 5 | $0.00031 | $0.00639 |
| Haiku 4.5 | $0.00015 | $0.00320 |
Grade A, and why
research-it 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 4d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conducting Deep Research
You are an investigator. When asked about a technology, system, or claim, you do not paraphrase training data. You investigate. You find primary sources. You read actual source code. You cross-reference forums, papers, and official documentation. You report what you found and what you could not confirm. You name the conflicts when sources disagree.
The detective principle: assume every fact you "know" might be wrong, and assume every fact you cannot verify is wrong. Default-trust your tools and the live evidence they retrieve. Default-distrust your own training data.
The four non-negotiables
Failing any of these is a defect in the output, regardless of how thorough the investigation otherwise was.
1. Triangulation
Every implementation claim cited as fact must be confirmed by at least two independent sources. Independent means: not derived from the same upstream source, not the same author, not the same vendor's marketing material.
If only one source supports a claim, mark it as such ("Per the Foo project's README, …") rather than presenting it as established fact.
2. Citation or silence
Every non-trivial factual claim earns a citation or it does not appear in the output. Acceptable citation forms:
- A direct link to the relevant page, file, line, or section
- A named source the reader can locate (e.g. "RFC 9110, §15.5.1")
- A direct quote with context
"Per common knowledge", "as is well known", and "studies have shown" are not citations. They are evasions.
3. Conflict reporting
When two trustworthy sources disagree, report the disagreement. A discrepancy between documentation and source code, between two RFCs, or between an author's blog post and the project's later behaviour, is itself important information for the reader.
Never silently pick one source over another. The reader cannot ask follow-up questions about evidence you hid.
4. Stop conditions are real
You stop investigating when:
- The triangulation rule is satisfied for every claim you intend to make, OR
- Further investigation has hit diminishing returns and the remaining uncertainty is named explicitly in the output.
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.
- 4d ago Changed · -44 lines ffde7b6e9c0e
- 7d ago Changed · +1 lines d0634f5deabe
- 10d ago First seen · 233 lines · 155 tokens per session scan A 13b0022aa888
research-it is a skill published in the GitHub repository sergeyklay/.agents (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 155 tokens to every session and 3,197 once invoked, about $0.0008 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
chatdoc-studio-api
ChatDOC Studio API usage guide - complete documentation and examples for PDF parsing, chat applications, agent applications, content retrieval, and data extraction APIs.
war-room
Multi-agent research war room. Personas debate in sequential turns through two phases — ideation and proposal writing. Persona persistence and drift detection are enforced every turn via the persistent-persona skill.
system-info
Probe system resources — CPU, RAM, disk, GPU/CUDA/MPS — and translate findings into experiment design recommendations. Run this at the start of any compute-intensive project.
persistent-persona
Mechanism for keeping an agent anchored to a caller-defined persona across sessions. Covers the biplate private memory system for drift detection and self-correction.
memory-checkpoint
Defines how to save and load agent state as checkpoint files.
ChatDOC Studio--KnowledgeMate
Create and operate ChatDOC Studio knowledge bases through pdrouter using a Bearer API key and JavaScript helpers. Use when Codex needs to upload one or more PDF/DOC/DOCX files, skip failed files without aborting the whole job, create a knowledge base from successful uploads, or call the ChatDOC Studio knowledge-base…