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-configuregit 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-configure)<a href="https://agentmods.dev/skills/usewire/wire-memory/wire-configure"><img src="https://agentmods.dev/badge/skills/usewire/wire-memory/wire-configure/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-configure"><img src="https://agentmods.dev/badge/skills/usewire/wire-memory/wire-configure.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.00015 | $0.00272 |
| Opus 5.5 | $0.00006 | $0.00109 |
| Sonnet 5.5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
wire-configure 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 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.
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
Configure Wire Memory
Read ~/.wire-memory/config.json. If it doesn't exist, tell the user to run /wire-connect first and stop.
Display the current transcript capture settings:
- Enabled: true/false
- Hooks: which events trigger capture (PreCompact, Stop, or both)
- Min turns: minimum session length before capturing
Ask the user what they'd like to change:
- Enable/disable transcript capture - automatically uploads session transcripts to the Wire container. Secrets are redacted, tool results are stripped.
- When to capture - before compaction + end of session (recommended), before compaction only, or end of session only
- Minimum session length in turns (default: 4)
Note: Transcript capture is only available on Claude Code. Cursor does not provide transcript file access to hooks.
Update ~/.wire-memory/config.json with the new settings. The transcripts key should look like:
{
"transcripts": {
"enabled": true,
"hooks": ["PreCompact", "Stop"],
"minTurns": 4
}
}
Show the user what was saved. Changes take effect immediately.
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 · 37 lines · 15 tokens per session scan A 8eb079ea22f1
wire-configure is a skill published in the GitHub repository usewire/wire-memory (10 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 272 once invoked, about $0.0001 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-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…