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 arch3rPro/Ark-Space --skill researchgit clone --depth 1 https://github.com/arch3rPro/Ark-SpaceWrote 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/arch3rpro/ark-space/research)<a href="https://agentmods.dev/skills/arch3rpro/ark-space/research"><img src="https://agentmods.dev/badge/skills/arch3rpro/ark-space/research/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/arch3rpro/ark-space/research"><img src="https://agentmods.dev/badge/skills/arch3rpro/ark-space/research.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.00044 | $0.01044 |
| Opus 5.5 | $0.00018 | $0.00418 |
| Sonnet 5.5 | $0.00009 | $0.00209 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
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 3d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
Use the installed arks CLI for long-running, Provider-backed synthesis. Start with research.run, then review its consequential conclusions and fill specific evidence gaps. Search and Fetch support that review; they are not a substitute for the initial Research run. The web Skill can guide those operations, but the review instructions below also work without an installed sibling Skill.
Readiness
- Run
arks --version. If unavailable, explain that ArkSpace CLI is required and ask before changing the user's environment. - Run
arks doctor --jsonwhen Provider readiness is unknown. If credentials are missing, direct the human to runarks setupin a trusted local terminal. Never ask for an API key in conversation or place one in a command argument. - Ask before changing configuration or the user's environment. Force Exa or Tavily only when the user requests it; otherwise preserve configured key handling and safe fallback.
Scope
Write a concrete prompt that states:
- the question, audience, intended decision, and what a useful answer must establish;
- date, geography, or entity boundaries;
- required comparisons and exclusions;
- source requirements for consequential claims;
- the desired report structure and any deadline.
Clarify only missing information that would change the investigation or deliverable; otherwise state assumptions and proceed. Scope the extra source-review calls separately from the remote job using the bounds in Evidence review.
Choose concise for a narrow answer, standard for an ordinary multi-source report, and deep only when broader coverage justifies higher latency and Provider cost. Depth selects Provider quality controls, not a guaranteed number of research passes. Protocol v1 has an operation timeout, not a common hard cost or query budget.
Run
Create a temporary Protocol v1 request:
{
"protocolVersion": 1,
"capability": "research.run",
"input": {
"prompt": "Compare the current authentication models of these APIs. Prefer official documentation, cite material claims, and identify unresolved differences.",
"depth": "standard",
"timeoutMs": 600000
}
}
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.
- 3d ago Changed · +5 lines e7b546a8fc9f
- 1mo ago Changed · +3 lines 5f33d219953b
- 1mo ago First seen · 69 lines · 44 tokens per session scan A a1d070f14452
research is a skill published in the GitHub repository arch3rPro/Ark-Space (1 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 1,044 once invoked, about $0.0002 per session on Opus 5.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-10.
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…