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 DavidROliverBA/ArchitectKB --skill wipegit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/wipe)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/wipe"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/wipe/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/davidroliverba/architectkb/wipe"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/wipe.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.00000 | $0.02182 |
| Opus 5 | $0.00000 | $0.01091 |
| Sonnet 5 | $0.00000 | $0.00436 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
wipe 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 9d 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wipe
Generate a context handoff summary, clear the session, and resume in a fresh conversation. Detects environment and provides automated (tmux) or manual workflow.
Usage
/wipe
/wipe quick # Minimal handoff, just essentials
/wipe detailed # Comprehensive handoff with full context
Instructions
When the user invokes /wipe:
Phase 1: Detect Environment
First, check the terminal environment:
echo "Environment Detection:"
echo "TMUX: ${TMUX:-not set}"
echo "TERM_PROGRAM: ${TERM_PROGRAM:-not set}"
echo "TERM: $TERM"
if [ -n "$TMUX" ]; then
echo "MODE: tmux (automated wipe available)"
tmux display-message -p 'Session: #{session_name}:#{window_index}.#{pane_index}'
else
echo "MODE: manual (clipboard workflow)"
fi
Phase 2: Generate Handoff Summary
Create a structured summary of the current session. Use this format:
## What we're working on
- [Primary task or topic from this session]
## Current state
- [Where we left off - be specific]
- [Any pending questions or decisions]
## Key decisions made
- [Important choices, conclusions, or agreements]
- [Technical decisions with rationale]
## Recent changes
- [Files modified with brief description]
- [Commands run or actions taken]
## Important context
- [Technical constraints or requirements]
- [User preferences discovered]
- [Project-specific facts needed to continue]
## Next steps
- [Immediate next action to take]
- [Any blocked items or dependencies]
Guidelines for generating the handoff:
- Be concise but complete - this will be the only context in the new session
- Include file paths for any files that were being edited
- Mention any errors encountered and their status (fixed/pending)
- Note any user preferences expressed during the session
- Skip sections that don't apply (empty sections waste tokens)
Phase 3: Execute Wipe
Based on the detected environment:
If tmux is detected (automated):
Present the handoff summary to the user, then provide this script:
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.
- 9d ago First seen · 358 lines · 0 tokens per session scan A a654e4e2c09f
wipe is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,182 tokens. 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-09-03.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.