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/runxhq/runx/answer-from-docsnpx skills add runxhq/runx --skill answer-from-docsgit clone --depth 1 https://github.com/runxhq/runxWhat 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.00035 | $0.01064 |
| Opus 5 | $0.00017 | $0.00532 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
answer-from-docs 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answer From Docs
Use this skill when the source material is already in hand and the operator needs one answer that can be checked against it. The corpus is the complete evidence boundary for the run. The skill does not search the web, fetch current documentation, consult private state, or fill gaps from the agent's general knowledge.
The useful result is not merely fluent text. A grounded result binds the corpus through a native digest, names the source for every citation, and preserves an exact quotation that the deterministic finalizer can find in that source. An unsupported result is also useful: it says what evidence is absent instead of turning a plausible guess into product documentation.
Evidence boundary
Supply:
question: one concrete question.corpus: a small, bounded array of source objects. Every source needs a stableid, a human-readabletitle, and non-emptytext.
Keep only material relevant to the question in the corpus. Runner inputs are
control data, not a document store. Admit large immutable files with Runx's
artifact tools, retrieve the necessary bounded pages, and then call this skill
with the resulting small source packet. Use extract first when the material
must be cleaned or structured. Use knowledge-router, research, or
deep-research when the sources still need to be found.
Source order is not authority. Prefer direct, specific language over a vague summary. If two sources disagree, preserve the conflict and refuse a single unqualified answer unless the corpus itself establishes precedence.
Decision procedure
- Read the question literally. Do not broaden it to a nearby question the corpus happens to answer.
- Treat the supplied sources as exhaustive for this run. Outside knowledge can help interpret language, but it cannot support a claim.
- Find the smallest set of passages that directly supports the answer.
- Draft a concise answer. Every material statement needs a citation with the
source
idand an exact quotation copied from that source'stext. - Use
unsupportedwhen the evidence is absent or too weak. Name the missing policy, limit, procedure, or source inkb_gaps. - Use
conflictedwhen supplied sources materially disagree. Record the conflict and the evidence needed to resolve it. - Let the deterministic finalizer verify corpus shape, source membership, exact quotations, the native corpus digest, and terminal result shape. Invalid evidence cannot seal as a grounded answer.
What ships with it
2 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 First seen · 108 lines · 35 tokens per session scan A 55b3d2e3558b
answer-from-docs is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed 3d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,064 once invoked, about $0.0002 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-30.
Other skills, from other repositories
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
beevibe-verify-pr
CI verification before marking a PR-bearing task done. Use BEFORE calling mcpbeevibeupdateprogress(done) on any session whose deliverable is a pull request — including the first dispatch (you opened the PR with gh pr create) and any revision dispatch (you pushed new commits to an existing PR). Watches the PR's…
beevibe-pre-task-setup
Cold-start git workspace setup for a fresh beevibe task. Use at the start of a session whose intent has a block but NO or block — i.e. the first dispatch of this task. Checks for an existing repo clone, pulls the base branch if present (clone if missing), prunes any per-task worktrees from earlier tasks whose work has…
beevibe-use-repo
You are the child agent inside a fresh Docker sandbox. Borrow the given GitHub repo, produce a real artifact for the goal, and export it. Do not review the repo. The proof is that it works.
beevibe-discover-repo
Find the best GitHub repo for a goal, then call userepo to run it in a sandbox. Use whenever the user's goal requires a capability you don't have natively and you haven't been given a specific repo.
minecraft-async
Manage a preinstalled local Minecraft Java client asynchronously for CTF and automation workflows. Use when an agent needs to launch Minecraft in offline mode with alternate usernames, inspect Minecraft logs, focus or type into the X11 game window, send chat or slash commands quickly, or join a multiplayer server by…