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/anamized/superagenticmcp/memory-scopenpx skills add ANAMIZED/SuperAgenticMCP --skill memory-scopegit clone --depth 1 https://github.com/ANAMIZED/SuperAgenticMCPWhat 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.00023 | $0.00139 |
| Opus 5 | $0.00012 | $0.00069 |
| Sonnet 5 | $0.00005 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
memory-scope 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 2d 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.
What it actually says
Memory Scope Skill
Workflow
- On run complete, file receipt + key artifacts into the scope graph.
- Link nodes by mission, server, and capability.
- Surface on the board memory constellation.
Rules
- Preserve provenance and timestamps on every node.
- Do not drop failed runs — file them with status=failed.
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.
- 2d ago First seen · 23 lines · 23 tokens per session scan A fdc11e34e303
memory-scope is a skill published in the GitHub repository ANAMIZED/SuperAgenticMCP (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 23 tokens to every session and 139 once invoked, about $0.0001 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
multi-agent-workflow
Create and run multi-agent workflows on Server OS.
repo-bootstrap
Automate full ANAMIZED product repo structure (Server OS parity) including USDC, Stripe, badges, CI, skills, AGENTS.md.
multi-agent-workflow
Orchestrate sequential multi-agent workflows under a shared budget on OpenMesha. Use when a goal needs planner/researcher/worker roles or council-style decomposition.
cost-control
Enforce and inspect token/dollar budgets for Server OS agents. Use when the user asks about agent spend, budgets, cost ledgers, or wants to prevent runaway token usage.
governance-audit
Inspect Server OS policy decisions, capability grants, and the audit log.
deploy-verify
Deploy Server OS and run the official end-to-end verification suite.