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 sprngr/rubber-duck --skill duck-tapegit clone --depth 1 https://github.com/sprngr/rubber-duckWrote 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/sprngr/rubber-duck/duck-tape)<a href="https://agentmods.dev/skills/sprngr/rubber-duck/duck-tape"><img src="https://agentmods.dev/badge/skills/sprngr/rubber-duck/duck-tape/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/sprngr/rubber-duck/duck-tape"><img src="https://agentmods.dev/badge/skills/sprngr/rubber-duck/duck-tape.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.00064 | $0.04739 |
| Opus 5 | $0.00032 | $0.02370 |
| Sonnet 5 | $0.00013 | $0.00948 |
| Haiku 4.5 | $0.00006 | $0.00474 |
Grade A, and why
duck-tape 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 11d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session memory management 🦆📼. Context hygiene, persistent memory, session state handoff.
Purpose
Two-tier memory management for active sessions.
- Tier 1 (persistent):
CONTEXT.mdin cwd. Long-term, repo-tracked. 7 fixed sections, deterministic merge. - Tier 2 (working):
.duck-tape/<session_id>.state.md. Short-term, not committed. Agent State schema. Staging input for CONTEXT.md merge.
Preserve fidelity, keep interruption low.
Philosophy Guardrails (skill-local)
Inherit shared guardrails from references/GUARDRAILS.md.
- ask 1-3 targeted clarifying questions when context is incomplete
- state assumptions explicitly when evidence is missing
Skill-specific delta:
- Persistent artifact safety: CONTEXT.md is long-lived and likely committed. Redaction is non-negotiable before any write.
- Session state safety:
.duck-tape/<id>.state.mdis workspace-local but may be read by next agent. Redaction applies. - Rotation cap: max 10 state files in
.duck-tape/. Eviction precedence: auto dropped first, then recovered, then manual. - Pre-compact marker (
.duck-tape/.last-compact) is harness-written, non-semantic. No approval required for marker write.
Activation
State-only (default): write session state file. Signals: /duck-tape, "save session state", "checkpoint session".
Merge (CONTEXT.md): write state file plus merge into CONTEXT.md. Signals: "compact session", "update CONTEXT.md", "persist memory", /duck-tape merge.
Resume: detect compaction and reload checkpoint. Signals: /duck-tape resume, "resume session". Read-only when manual checkpoint exists. If only auto-checkpoint or no state file, invokes LLM-assisted recovery that writes -recovered.state.md (approval required).
Method
1. Redact incoming content
Scan session content for secrets/PII: API keys, passwords, tokens, connection strings, env var values, personally identifiable information. On detection: reject flagged content, report findings, ask user to redact source or confirm mask-in-place (<REDACTED>). If a write would contain raw secrets, reject it; write masked content only after user confirmation. Applies to both tiers.
What ships with it
20 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.
- examples/bootstrap-CONTEXT.md 463 B
- examples/CHANGELOG.md 419 B
- examples/CONTEXT.md 2.1 KB
- examples/STATE.md 1.2 KB
- hooks/claude-code.hooks.json 291 B
- hooks/claude-code.hooks.windows.json 312 B
- hooks/copilot.hooks.json 325 B
- hooks/extract-raw.ps1 15 KB runs code
- hooks/extract-raw.sh 12 KB runs code
- hooks/extract-state.ps1 15 KB runs code
- hooks/extract-state.sh 11 KB runs code
- hooks/opencode.plugin.js 13 KB runs code
- hooks/pre-compact.ps1 1.1 KB runs code
- hooks/pre-compact.sh 1.0 KB runs code
- README.md 15 KB
- references/GUARDRAILS.md 757 B
- references/HOOKS_GUIDE.md 11 KB
- references/OUTPUT_SCHEMA.md 2.9 KB
- references/SCHEMA.md 6.4 KB
- references/STATE_SCHEMA.md 4.9 KB
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.
- 11d ago First seen · 327 lines · 64 tokens per session scan A 0dbb7ea1057c
duck-tape is a skill published in the GitHub repository sprngr/rubber-duck (8 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 4,739 once invoked, about $0.0003 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
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.
grimoire
Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why. Also the place for complaints, feedback and settings changes about this skill itself.
ln-31-performance-optimizer
Profiles and improves a measured latency, throughput, CPU, memory, or I/O problem. Not for speculative tuning or cosmetic refactoring.