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 anotb/driftglass --skill answer-missiongit clone --depth 1 https://github.com/anotb/driftglassWrote 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/anotb/driftglass/answer-mission)<a href="https://agentmods.dev/skills/anotb/driftglass/answer-mission"><img src="https://agentmods.dev/badge/skills/anotb/driftglass/answer-mission.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.00060 | $0.01791 |
| Opus 5 | $0.00030 | $0.00896 |
| Sonnet 5 | $0.00012 | $0.00358 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
answer-mission 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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answer from Driftglass
Use Driftglass as the evidence source. Do not answer from general memory when the connected instance is available. Choose one route.
Shape the live card
Answer the user's question with the information that changes the answer. Do not write a changelog, source recap, or status report.
- Default to
answerMode: synthesisfor questions about state, trajectory, causes, implications, comparison, or what changed broadly. - In synthesis mode, start with a required cited
thesisthat gives the answer and causal spine. Stop when the question is answered; do not pad it to fill a format. It may stand alone. Add one to fourkeyJudgments, an optionalcompetingExplanation, and zero to twowatchForsignals only when each extra block adds a distinct fact, mechanism, implication, or falsifier. Give every included judgment a factualtitleand concrete evidence. Omit every extra block that does not add one. - Use
answerMode: decisiononly when the user explicitly asks for a choice, action, test, deferral, or rollback rule. Provide citedwhatChangedandwhyItMatters, then include exactly the requesteddecisionrows: a boundedtestNowwith comparison and sample or timebox, an observabledeferUntilcondition, and/or a measurablerollbackIfthreshold with its evaluation window. A generic recommendation gets only the single most relevant row. These parameters are ChatGPT judgment anchored by cited evidence, not claims that a source states them verbatim. Do not add synthesis fields orwatchNextin decision mode. - Lead with claims. Prefer dates, quantities, mechanisms, and consequences to adjectives or stacked qualifiers. Connect developments only when the evidence supports the connection.
- Every rendered section needs one to three exact public citation URLs from the evidence result. Keep URLs out of prose and put them in that section's
citationUrls. - Do not narrate source counts, source families, coverage, evidence mechanics, tools, receipts, or the briefing process in answer fields. Keep limits in the collapsed source disclosure.
- After
present_briefsucceeds, stop. The live card is the answer, so do not add a prose recap or generic conclusion.
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.
- 7d ago First seen · 73 lines · 60 tokens per session scan A 634c170a3863
answer-mission is a skill published in the GitHub repository anotb/driftglass (1 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 1,791 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
owd-albatross
Connect, initialize, resume, or coordinate MDevolved Projects from Albatross using its agent.config.json stdio MCP surface, a pinned OAuth bridge, qualified tool names, workspace prompt continuity, path forks, resets, and independently attributable participant identities. Use when a repository runs Albatross, contains…
owd-eve
Connect, initialize, resume, or coordinate MDevolved Projects from an Eve agent using Eve's standard remote MCP connection, user-scoped Vercel Connect OAuth, qualified tool names, durable Project continuity, and independently attributable agent identities. Use when an Eve repository has agent/connections, when adding…
owd-obsidian-mind
Connect, initialize, resume, or coordinate an Obsidian Mind vault with MDevolved while preserving its local qmd/om MCP runtime, native note layout, scoped memories, private-note rules, and multi-agent writer safety. Use when a vault-manifest.json identifies template obsidian-mind, when adding MDevolved beside Obsidian…
mdevolved-albatross
Connect or resume an Albatross workspace with MDevolved through its stdio MCP bridge, preserving runtime-local execution and owner-approved Project authority.
mdevolved-eve
Connect or resume an Eve agent with MDevolved through a user-scoped remote MCP connection while preserving Eve runtime identity and MDevolved Project continuity.
mdevolved-obsidian-mind
Connect an Obsidian Mind workspace to MDevolved while preserving Mind's local graph and memory runtime, native note layout, and owner-controlled write boundary.