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 task-close-postmortemgit 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/task-close-postmortem)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/task-close-postmortem"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/task-close-postmortem/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/task-close-postmortem"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/task-close-postmortem.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 Agent Snooping · line 209 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00094 | $0.02553 |
| Opus 5.5 | $0.00038 | $0.01021 |
| Sonnet 5.5 | $0.00019 | $0.00511 |
| Haiku 4.5 | $0.00009 | $0.00255 |
Grade A, and why
task-close-postmortem 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 23d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task-Close Postmortem
Captures a short reflection at task close, maps any surfaced gaps to concrete Bridge-File-Improvement-Proposals, and writes both back as structured artifacts.
The skill is always optional and always interruptible — every question is
skippable, and skipping all six leaves the task unchanged from today's behavior.
Default-on (per bridge-config.yaml.learning.postmortem.enabled) but cost-light:
fast-path through all six skips is <20 seconds.
When this skill runs
- Auto, via
task-sync.mdPhase 3b — every time a task closes, after the dual_doku self-check passes and before the 3-step move. - Manual — when the user says any of: "/postmortem the last hour", "reflect on the piece just finished", "post-mortem this", "what did we learn from X". In manual mode the scope is not bound to a task folder — the skill reflects on the recent activity (last log.md entries, recent commits, recent file edits). No frontmatter writes happen in manual mode; output is only the proposals.
Inputs
Auto mode:
work/tasks/<slug>/STATUS.md— the task being closedworkflow/contexts/<context>.yamlif STATUS references a context- recent entries from
work/log.md(last 24h or all entries since taskcreated)
Manual mode:
- last N log.md entries (N defaults to last 10, or "the last hour")
- recent uncommitted git diff in this Bridge repo and any other repos touched
The six questions
(Full script in references/postmortem-questions.md.)
Surface them one at a time. Accept skip-phrases from
bridge-config.yaml.learning.postmortem.skip_phrases — default
["skip", "next", "—", "no", "next", "."]. If
cutdown_after_skips (default 3) consecutive skips occur, switch
to Cutdown mode for the remaining questions: ask only the single
catch-all "anything else worth noting?". Empty answer → done.
| # | Question (EN) | Writes to |
|---|---|---|
| 1 | Time invested? | frontmatter time_invested |
| 2 | Estimate vs actual? | frontmatter estimate_vs_actual |
| 3 | What went well? | body ## Postmortem → "What went well" |
| 4 | What burned time? | body ## Postmortem → "What did not go well" |
| 5 | Did the bridge fail you? | frontmatter bridge_gaps[] + body |
| 6 | Concrete improvement? | proposal file + body |
What ships with it
3 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.
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.
- 23d ago Changed · -74 tokens per session a0ba80a5e49e
- 26d ago Changed · +9 lines 27a5ee3316c3
- 1mo ago First seen · 212 lines · 168 tokens per session scan A 3f5da87a0329
task-close-postmortem is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 2,553 once invoked, about $0.0004 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
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
paperclip-distill
Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.