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 bks-lab/open-bridge --skill archivegit clone --depth 1 https://github.com/bks-lab/open-bridgeWrote 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/bks-lab/open-bridge/archive)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/archive"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/archive/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/bks-lab/open-bridge/archive"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 26 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00074 | $0.00526 |
| Opus 5.5 | $0.00030 | $0.00210 |
| Sonnet 5.5 | $0.00015 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
archive 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 24d 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
Archive
Periodic archive workflow. Read the referenced file ONLY when triggered.
The period is configurable — bridge-config.yaml work.archive_cadence
(weekly default, then bi-weekly / monthly / quarterly / yearly).
The same key drives /briefing's staleness warning, so the reminder and the
archiver always agree on what "overdue" means.
Archiving distils before it resets: work/archive/ has no reader, so
without a distil step archiving would be forgetting with a backup. Phase 5
proposes durable facts for the memory base — which is loaded every session
— and never writes one without confirmation
(rules/learning-autonomy.md).
Arguments
| Argument | Effect | Default |
|---|---|---|
(none) |
Archive every closed period in the log, one file each, per work.archive_cadence |
— |
--force |
Archive the current (in-progress) period too | false |
--no-distil |
Skip Phase 5; archive without proposing memories | false |
Prerequisites
bridge-config.yaml with work.enabled: true. If not: inform and exit.
Decision Tree
User wants to...
├── Archive the period → Read references/workflow.md
├── Change how often it archives → bridge-config.yaml work.archive_cadence
├── Are we behind on anything? → Read skills/briefing/references/upstream-summary.md
└── Questions about archiving → Answer from this file
Activity Types
| Symbol | Name |
|---|---|
| 🧪 | Testing |
| 💻 | Development |
| 🔬 | Analysis |
| 📋 | Planning |
| 📝 | Documentation |
| 🔧 | DevOps |
| 📅 | Meeting |
| 📧 | Communication |
| 📁 | Documents |
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.
- 24d ago Changed · -1 lines · -27 tokens per session c5331473bf95
- 26d ago Changed · +11 tokens per session 118fc2592cba
- 1mo ago First seen · 64 lines · 90 tokens per session scan A d8c547f2deb1
archive is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 526 once invoked, about $0.0003 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
wiki-ingest
Use when an operation issue asks to ingest a captured raw/ source into the LLM Wiki, or the user says "ingest ". Create durable source, entity, concept, synthesis, index, and log pages; use paperclip-distill for Paperclip bundles.
wiki-lint
Use when an LLM Wiki operation issue is a lint or health check. Audit for contradictions, orphans, weak provenance, broken links, missing concept pages, and index/log drift; return triage findings without auto-fixing.
para-memory-files
Use a file-based PARA memory system to store, retrieve, and organize durable knowledge across sessions. Trigger on saving facts, daily notes, entity records, weekly synthesis, recall, tacit user patterns, or plan memory.
memclaw
The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control. Consult it at the start of a task to recall prior decisions, findings, and rules before acting, and write outcomes, decisions, and lessons as work completes. Use whenever a caura…
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
state-management
STATE.md reading, writing, and field-level updates. Provides cross-session state persistence via .planning/STATE.md with structured fields for current task, completed phases, blockers, decisions, and quick tasks.