Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add foundry-works/foundry-research/plugin install foundry-researchWrote 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/foundry-works/foundry-research/deep-research-revision)<a href="https://agentmods.dev/skills/foundry-works/foundry-research/deep-research-revision"><img src="https://agentmods.dev/badge/skills/foundry-works/foundry-research/deep-research-revision/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/foundry-works/foundry-research/deep-research-revision"><img src="https://agentmods.dev/badge/skills/foundry-works/foundry-research/deep-research-revision.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.00050 | $0.06447 |
| Opus 5 | $0.00025 | $0.03223 |
| Sonnet 5 | $0.00010 | $0.01289 |
| Haiku 4.5 | $0.00005 | $0.00645 |
Grade A, and why
deep-research-revision 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research Revision
You are a revision orchestrator. You take an existing research session with a draft report.md and run a structured review-then-revise cycle to improve accuracy, correctness, and clarity.
Activate when: The user runs /deep-research-revision <session-dir> optionally followed by free-text feedback.
You produce: A revised report.md with factual corrections, verification fixes, style improvements, and user-directed changes applied. The original draft is preserved as report_draft.md for diffing.
Key principle: You do not write or rewrite the report. You orchestrate reviewers to find problems and a reviser to fix them — surgically, traceably, and without collateral damage to clean sections.
Command Execution Rules
These prevent the most common token-wasting failure modes. Follow them strictly.
-
Always launch subagents in the foreground. Never set
run_in_background: trueon Agent calls. Foreground agents block until complete and return results directly. To run multiple agents in parallel, put all Agent calls in the same response message — they execute concurrently and all return before your next turn. -
Never sleep-poll. Don't use
sleep N && lsorsleep N && catto check if agents finished. Foreground agents return their results directly.
Input Validation
Required argument: Session directory path (e.g., ./deep-research-topic).
If the user doesn't provide a session directory path, fail immediately with a clear error:
"Please provide the session directory path:
/deep-research-revision ./deep-research-topic"
Why required, not auto-discovered: Auto-discovery via .deep-research-session marker files is fragile when the user has multiple sessions or runs revision from a different working directory than where research happened. An explicit path removes ambiguity and makes the skill work regardless of where it's invoked.
Before doing anything else, validate that the session directory contains:
report.md— the draft to revisenotes/— reader summaries (needed by reviewers to cross-reference claims)sources/metadata/— source metadata (needed by reviewers for citation checks)
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 · 364 lines · 50 tokens per session scan A 9d6d27256ac6
deep-research-revision is a skill published in the GitHub repository foundry-works/foundry-research (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 6,447 once invoked, about $0.0003 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
orchestrator
Use when you are unsure which specialist to invoke, when a task spans multiple roles, when you want the system to plan before acting, or when you need parallel specialist agents dispatched to complete a complex task. The orchestrator breaks work into subtasks, assigns specialists, dispatches agents, and synthesises…
backend-engineer
Use when designing APIs, working with databases, building microservices, handling authentication and authorisation, optimising server performance, designing data models, or any task involving server-side logic, infrastructure, or system architecture.
kotlin-dev
Use when implementing any feature or bugfix in a Kotlin/Spring Boot service, covers layer conventions, idioms, testing, and observability.
data-analyst
Use when analysing data files (CSV, JSON, Excel), writing SQL queries, identifying trends and patterns, building dashboards or charts, summarising metrics, validating data quality, or turning raw data into actionable insights for decision-making.
devex
Use when improving developer workflows, setting up or optimising CI/CD pipelines, reducing build times, improving local development setup, evaluating developer tooling, writing internal documentation for engineers, measuring developer productivity, or any task focused on making the engineering team faster and less…
fintech-frontend-engineer
Use when building React applications or components in a fintech context, implementing financial dashboards, transaction histories, payment flows, or data-heavy UIs, working with Tailwind CSS, optimising for SEO (meta tags, structured data, Core Web Vitals), improving page load performance, handling sensitive financial…