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 wefio/NodeMemoryGraph --skill working-state-maintenancegit clone --depth 1 https://github.com/wefio/NodeMemoryGraphWrote 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/wefio/nodememorygraph/working-state-maintenance)<a href="https://agentmods.dev/skills/wefio/nodememorygraph/working-state-maintenance"><img src="https://agentmods.dev/badge/skills/wefio/nodememorygraph/working-state-maintenance/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/wefio/nodememorygraph/working-state-maintenance"><img src="https://agentmods.dev/badge/skills/wefio/nodememorygraph/working-state-maintenance.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.00072 | $0.00988 |
| Opus 5.5 | $0.00029 | $0.00395 |
| Sonnet 5.5 | $0.00014 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
working-state-maintenance 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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working-state maintenance
Keep the smallest provisional snapshot that lets a capable reader choose the next authorized action with the available evidence. A working state is not a journal, a second task contract, or proof of completion. This procedure works without reading a task-semantics design document.
Maintain the current snapshot
- Reconcile the visible state with the latest user request and completed tool results. Reuse what is already available; read an owner or evidence reference only to settle a missing or conflicting fact. Replace the old task when the request changes; do not carry its pending actions into the new task or invent a semantic task identifier. A new request can end a previous wait for input.
- Check any new completion claim against the actual result: exit status, assertions, verification scope, and the relevant owner. A returned tool call, live process, or written artifact is not a passing check. Distinguish planned, attempted, implemented, verified, and unresolved work. Unknown stays unknown; do not expand a targeted pass into a full verification claim.
- Keep an item only if removing it could change the next action, lose an unmet obligation, violate a constraint, or hide evidence needed to resume. Preserve necessary exact values, permission boundaries, unresolved assumptions, and accessible evidence references. Detailed logs and completed-task history belong at their existing owners, not in this snapshot.
- Rewrite the whole current snapshot rather than appending a progress entry. Remove superseded observations, resolved blockers, and irrelevant runtime details; retain an unresolved blocker until evidence settles it. A PID or test count belongs here only while a current decision depends on it. Do not remove a necessary condition merely to meet a line target.
- Use only the fields the task needs: goal, relevant verified progress, current step, next action, blockers, constraints, or evidence. Omit empty fields and repeated standing instructions. A small task can use one sentence; no fixed template, field count, or length proves sufficiency.
- Before writing, check whether the reader can identify the next action and its limits without the original Agent's private reasoning. Write only when the current state materially changes. On completion leave a short result, remaining limits, and an evidence entry point, not a deployment narrative.
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.
- 10d ago Changed · +2 lines a286d14a1a6c
- 13d ago First seen · 76 lines · 72 tokens per session scan A 9662711d0c45
working-state-maintenance is a skill published in the GitHub repository wefio/NodeMemoryGraph (0 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 988 once invoked, about $0.0003 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-10-17.
Other skills, from other repositories
reminder
Set reminders and manage todos with natural language. Uses built-in cron scheduling, no external service needed.
daily-briefing
Daily briefing aggregating weather, reminders, news, and calendar. Delivered on schedule via any channel.
calendar
Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.
email-assistant
Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.
skills-constitution
A set of rules that makes an agent check its memory and available skills before handling professional tasks such as coding, file work, data analysis, or deployment.
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…