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 tony/skills --skill foraygit clone --depth 1 https://github.com/tony/skillsWrote 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/tony/skills/foray)<a href="https://agentmods.dev/skills/tony/skills/foray"><img src="https://agentmods.dev/badge/skills/tony/skills/foray/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/tony/skills/foray"><img src="https://agentmods.dev/badge/skills/tony/skills/foray.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.00034 | $0.01479 |
| Opus 5.5 | $0.00014 | $0.00592 |
| Sonnet 5.5 | $0.00007 | $0.00296 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
foray 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 8d 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.
This is a copy
86% identical to research-foray — 50 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/research:foray
Research a topic, or assess a decision, so the work outlives the session: each run in a dated folder, each claim tied to a captured and pinned source, later runs building on earlier ones, and a report that leads with the answer.
User arguments: $ARGUMENTS
Pick the procedure
<topic.py> is scripts/topic.py in this plugin, at ../../scripts/topic.py from this skill's directory. Before the first command, resolve it once to an absolute path from this skill's base directory (known when the skill loads) and write that absolute path literally in every later command: shell variables do not persist between Bash calls. Parse the arguments with the script, never by hand. A wrapper skill (assess, status, continue, verify, report, release) hands you its step word and its arguments: write the step word, when there is one, then the arguments exactly as given, inside a quoted heredoc so the shell expands nothing:
$ python3 <topic.py> route --stdin <<'ARGS'
<step word> <arguments>
ARGS
route prints the step, the validated flags, the references to read, and the rest of the request as request, with topic set when that rest is one name or one quoted phrase; otherwise read the topic from request. It says when it inferred continue from --fill or --expand. On an error (an unknown option or an invalid value), report it and stop. With no step word, read the request and pick one:
- A new topic or question:
../../references/start.md. assess, or a new decision:../../references/start.mdin assessment mode, with../../references/assessment.md.status, "what research do I have", "where was I":../../references/status.md.continue, pick up, keep going, fill the gaps, dig deeper, expand:../../references/continue.md.verify, re-check sources, links, or quotes, or look for missed sources:../../references/verify.md.report, write or rewrite the report:../../references/report.md.releasenamed by the user:../../references/release.md. "Is it ready" without that word:checkper../../references/release.mdstep 1 alone. "Record a decision" and "export" run underrelease:../../references/release.mdstep 3 or 5.- Any other request to send, share, or hand off a report: finish the report and its
check, then offerreleasein the panel. Never release on your own initiative.
What ships with it
1 file 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.
- 8d ago Changed · +30 lines · +3 tokens per session f0e74c7bf372
- 15d ago Changed · +3 lines b71a158bee77
- 16d ago First seen · 51 lines · 31 tokens per session scan A 107b4d9cd2ed
foray is a skill published in the GitHub repository tony/skills (0 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,479 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to research-foray, differing in 50 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…