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/dizeldz20-ux/agent-shared-memory/graph-missionnpx skills add dizeldz20-ux/agent-shared-memory --skill graph-missiongit clone --depth 1 https://github.com/dizeldz20-ux/agent-shared-memoryWrote 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/dizeldz20-ux/agent-shared-memory/graph-mission)<a href="https://agentmods.dev/skills/dizeldz20-ux/agent-shared-memory/graph-mission"><img src="https://agentmods.dev/badge/skills/dizeldz20-ux/agent-shared-memory/graph-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.00107 | $0.00909 |
| Opus 5 | $0.00053 | $0.00454 |
| Sonnet 5 | $0.00021 | $0.00182 |
| Haiku 4.5 | $0.00011 | $0.00091 |
Grade A, and why
graph-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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graph Mission for Codex
Turn a broad request into a small, typed execution graph before doing expensive work. The graph is temporary execution state; ASM and the Obsidian vault are the durable knowledge system.
The useful distinction is:
- ASM recalls what the workspace already knows.
- The mission graph decides what this run still needs to do.
- Current files and live checks establish what is true now.
- ASM write-back makes verified outcomes available to later Claude, Codex, and Gemini sessions.
Activation boundary
Use this skill for an explicit $graph-mission request, two or more genuinely independent lanes, evidence-heavy research plus implementation, broad work whose success is not yet pinned down, or work likely to cross a compaction or session boundary.
If the task is one lookup, one localized edit, or a tightly coupled design/refactor, choose zero-shot or a short chain and do the work directly. State that the graph would cost more than it saves; do not manufacture ceremony.
Required workflow
- Read references/knowledge-loop.md and perform ASM recall before decomposing the request or inspecting mapped project files.
- Read references/compile.md and references/graph-architecture.md, then compile one objective, one checkable success signal, explicit non-goals, authorization boundaries, a sourced recall pack, and the cheapest graph that fits.
- Mirror the top-level nodes in the client plan. Share a concise mission brief in commentary and proceed without asking for redundant confirmation unless a real user decision or new authority is required.
- Read references/run.md before execution. Keep architecture, synthesis, conflict resolution, and final verification with the primary agent.
- Read references/evidence-gate.md before accepting any worker result or marking a node verified. A worker report is a lead, not proof.
- Use references/mission-schema.md when the run needs persistent lineage or is being resumed.
- Close the knowledge loop through ASM. Record only verified outcomes; create or update a canonical vault page only for knowledge that should remain durable beyond the handoff.
What ships with it
6 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.
- 5d ago First seen · 48 lines · 107 tokens per session scan A e6f5becbb0c4
graph-mission is a skill published in the GitHub repository dizeldz20-ux/agent-shared-memory (1 stars, last pushed 2d ago), licensed MIT. It adds 107 tokens to every session and 909 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…