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 usewire/wire-memory --skill wire-claimgit clone --depth 1 https://github.com/usewire/wire-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/usewire/wire-memory/wire-claim)<a href="https://agentmods.dev/skills/usewire/wire-memory/wire-claim"><img src="https://agentmods.dev/badge/skills/usewire/wire-memory/wire-claim/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/usewire/wire-memory/wire-claim"><img src="https://agentmods.dev/badge/skills/usewire/wire-memory/wire-claim.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.00023 | $0.00197 |
| Opus 5.5 | $0.00009 | $0.00079 |
| Sonnet 5.5 | $0.00005 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade B, and why
wire-claim scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SCRIPT="$(find ~/.claude/plugins ~/.cursor/plugins -path '*wire-memory*/skills/wire-claim/scripts/claim.mjs' -print -quit 2>/dev/null)" What it actually says
Claim Wire Memory Container
Locate and run the claim script with the Bash tool. The script is at scripts/claim.mjs inside this skill's own directory (skills/wire-claim/scripts/claim.mjs within the installed wire-memory plugin). The Bash tool's working directory may not be the skill directory — resolve to an absolute path before invoking:
SCRIPT="$(find ~/.claude/plugins ~/.cursor/plugins -path '*wire-memory*/skills/wire-claim/scripts/claim.mjs' -print -quit 2>/dev/null)"
node "$SCRIPT"
After the script opens the browser, the user should create an account and complete the onboarding flow. Once done, the container is permanently linked to their account.
If the container is already claimed, the script will update the local config and confirm.
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.
- 1mo ago First seen · 18 lines · 23 tokens per session scan B a68ed13cc7d2
wire-claim is a skill published in the GitHub repository usewire/wire-memory (10 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 197 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
checkpoint
Write the current working state (task, decisions, files touched, open problems, next steps) to .amber/STATE.md so it survives compaction and session restarts. Use when the user asks to checkpoint/save state, before risky long operations, when context feels heavy, or before ending a work session.
resume
Reload saved working state from .amber/ (STATE.md, FOCUS.md, checkpoint.md) and continue the previous task. Use when the user says resume/continue where we left off, or at the start of a session in a project that has an .amber directory.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
agent-common
Use when a cc10x agent starts a task: the shared preamble for the memory protocol, the contract format, and the output rules.
memory-protocol
A shared set of rules for using a persistent memory service across coding-agent sessions.
memory
Activate this skill when starting a new session, beginning a new task, saving knowledge, recalling past decisions, or after completing significant work. Also activate on errors to log them for pattern analysis. Relevant when the user asks about memory, past context, lessons learned, decisions history, project…