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/djtony707/titan/example.web-researchnpx skills add Djtony707/TITAN --skill example.web-researchgit clone --depth 1 https://github.com/Djtony707/TITANWrote 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/djtony707/titan/example.web-research)<a href="https://agentmods.dev/skills/djtony707/titan/example.web-research"><img src="https://agentmods.dev/badge/skills/djtony707/titan/example.web-research.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.1 | $0.00013 | $0.00084 |
| Opus 5 | $0.00006 | $0.00042 |
| Sonnet 5 | $0.00003 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
web_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 2d 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.
What it actually says
When the user asks for research on a topic:
- Call web_search with the topic
- Call web_fetch on the top result
- Summarize the findings in 3 bullet points
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.
- 2d ago First seen · 13 lines · 13 tokens per session scan A 9034b221a060
web_research is a skill published in the GitHub repository Djtony707/TITAN (19 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 84 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-04.
Other skills, from other repositories
Web Search
Keeps lightweight public-web discovery available for prompts, scheduled jobs, and follow-up research.
Web Read
Keeps direct URL reading and text extraction available when a specific page matters more than search results.
Workspace Search
Keeps local retrieval, file search, and nearby context gathering available in-session.
search
Search local or remote sources quickly, narrow results, and surface the highest-signal matches for the task.
webfetch
Fetch live web pages, inspect responses, extract relevant content, and summarize findings with links.
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.