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 agentmods add skills/nirholas/three.ws/research-assistantnpx skills add nirholas/three.ws --skill research-assistantgit clone --depth 1 https://github.com/nirholas/three.wsWrote 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/nirholas/three.ws/research-assistant)<a href="https://agentmods.dev/skills/nirholas/three.ws/research-assistant"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/research-assistant.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00940 |
| Opus 5 | $0.00013 | $0.00470 |
| Sonnet 5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
research-assistant 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 yesterday.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Assistant
When to use this skill
Use when the user asks about:
- Researching a crypto topic they're unfamiliar with
- Getting a comprehensive overview of a subject
- Comparing multiple options or approaches
- Understanding a complex technical concept
- Preparing a research brief or summary
Research Methodology
1. Scope Definition
Before starting research, clarify:
- Research question: What specifically does the user want to know?
- Depth level: Surface overview, moderate analysis, or deep dive?
- Time sensitivity: Is this about current state or historical context?
- Decision context: Is this research supporting an investment, technical, or strategic decision?
- Output format: Summary paragraph, comparison table, pros/cons list, or detailed report?
2. Source Hierarchy
Prioritize information sources by reliability:
| Tier | Source Type | Trust Level | Examples |
|---|---|---|---|
| 1 | On-chain data | Highest | Block explorers, Dune Analytics, DefiLlama |
| 2 | Official documentation | High | Protocol docs, whitepapers, GitHub repos |
| 3 | Audit reports | High | Trail of Bits, OpenZeppelin, Consensys Diligence |
| 4 | Reputable analysis | Medium-High | Messari, Delphi Digital, The Block Research |
| 5 | Community research | Medium | Mirror posts, governance forums, well-known researchers |
| 6 | News outlets | Medium | CoinDesk, The Block, Blockworks |
| 7 | Social media | Low-Medium | Twitter/X threads, Reddit (verify claims independently) |
| 8 | Anonymous claims | Low | Unverified Discord/Telegram messages |
Always cross-reference claims across multiple sources.
3. Research Structure
Organize findings into these sections:
- Executive summary: 2-3 sentence answer to the research question
- Background: Context needed to understand the topic
- Key findings: Numbered list of the most important discoveries
- Analysis: Deeper examination of findings with supporting data
- Risks and limitations: What could go wrong or what is uncertain
- Conclusion: Actionable takeaway aligned with the user's decision context
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.
- yesterday First seen · 98 lines · 26 tokens per session scan A 11580ae307bc
research-assistant is a skill published in the GitHub repository nirholas/three.ws (110 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 940 once invoked, about $0.0001 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
blockchain-cross-chain
Cross-chain protocols, IBC, LayerZero, Wormhole, Axelar, CCIP, bridges, atomic composability, shared sequencer, cross-chain message passing. Covers trust models (light clients, external validators, ZK proofs), bridge security, token representation (canonical, wrapped, native), relayer economics, and cross-chain…
blockchain-security
Use this skill when asked about blockchain security, smart contract auditing, DeFi threat modeling, blockchain incident response, bug bounty programs, economic security, formal verification of smart contracts, and blockchain-specific security analysis. Languages: Solidity, Python, Rust, Haskell. Covers threat modeling…
blockchain-testing
Use this skill when asked about testing smart contracts, Foundry tests, Hardhat tests, fuzz testing, invariant testing, property-based testing, formal verification, audit preparation, integration testing for dApps, and blockchain testing patterns. Covers Foundry cheatcodes, Echidna fuzzing, Certora verification…
xpr-network-dev
XPR Network (formerly Proton) blockchain development - proton-tsc smart contracts, @proton CLI and web SDK, RPC and Hyperion queries, DeFi (MetalX, Alcor, LOAN), NFTs, the XPR Agents job board, node and Hyperion operations. Use for anything mentioning XPR, Proton, or @proton packages.
blockchain-management
Use this skill when asked about blockchain project management, DAO governance, multi-sig operations, treasury management, tokenomics design, and web3 project methodology. Languages: Solidity, TypeScript, Python. Covers DAO governance frameworks (Compound Governor, Aave, Snapshot, Tally), multi-sig wallet operations…
modernize-move
Detects and modernizes outdated Move V1 syntax, patterns, and APIs to Move V2+. Use when upgrading legacy contracts, migrating to modern syntax, or converting old patterns to current best practices. NOT for writing new contracts (use write-contracts) or fixing bugs.