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 pushkalkumar/context-bridge --skill skillgit clone --depth 1 https://github.com/pushkalkumar/context-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/pushkalkumar/context-bridge/skill)<a href="https://agentmods.dev/skills/pushkalkumar/context-bridge/skill"><img src="https://agentmods.dev/badge/skills/pushkalkumar/context-bridge/skill/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/pushkalkumar/context-bridge/skill"><img src="https://agentmods.dev/badge/skills/pushkalkumar/context-bridge/skill.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.00089 | $0.01041 |
| Opus 5.5 | $0.00036 | $0.00416 |
| Sonnet 5.5 | $0.00018 | $0.00208 |
| Haiku 4.5 | $0.00009 | $0.00104 |
Grade A, and why
context-bridge 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
context-bridge
Persistent task memory across Claude Code sessions: checkpoints, stagnation detection, attempt replay, and planning. The backend auto-starts when a session begins and hooks checkpoint automatically. Everything you do goes through two CLI commands — never hand-build HTTP calls (raw API, only if the CLI is unavailable: references/api.md).
Record progress: context-bridge sync
Run at these moments — not every message:
- The user states or changes the session goal.
- A task completes and the next step is known.
- A blocker is hit (pass the exact error via
--blocker).
context-bridge sync \
--goal "Ship JWT auth" \
--task "Implement /login endpoint" \
--progress "/register done; /login returns 500 on bcrypt verify" \
--blocker "error: cannot find module 'bcrypt'" \
--next "Fix bcrypt import, then sign HS256 token"
--blocker is repeatable. Project ID and git state are gathered automatically.
The output is the plan. Act on it:
Plan:— execute it; on conflict with the user request, see Conflicts.Priority:— the active constraint for the session.stagnation Nwith N ≥ 3 — apply the stagnation protocol (below).confidencebelow 75% — surface the uncertainty before proceeding.⚠ Blocker class:— address that blocker type before retrying.⚠ Decompose:— split into subtasks of 30 minutes or less first.rule-basedsource — follow the plan exactly, do not improvise.
Record events: context-bridge event
context-bridge event failure --attempted "session cookies" --because "stateless API requirement"
context-bridge event adr --decision "HS256 signing" --reason "single service" --tradeoff "rotation needs redeploy"
context-bridge event outcome --result "auth suite green" --impact "auth feature complete"
Record failure when abandoning an approach (feeds blocker matching), adr on
architecture decisions, outcome when a significant result lands. Goal and task
default to the latest checkpoint's — override with --goal/--task if the
event belongs elsewhere.
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.
- 1mo ago First seen · 102 lines · 89 tokens per session scan A baa2f75cb46e
context-bridge is a skill published in the GitHub repository pushkalkumar/context-bridge (2 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 1,041 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
add-karpathy-llm-wiki
Add a persistent wiki knowledge base to a NanoClaw group. Based on Karpathy's LLM Wiki pattern. Triggers on "add wiki", "wiki", "knowledge base", "llm wiki", "karpathy wiki".
memory-management
Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
memcode
Use the enabled Memcode MCP connection to explicitly save approved facts and recall relevant memories across DeepChat conversations. Never save a transcript or retrieve memory automatically.
vellum-memory-v2-migration
Perform a one-time migration from memory v1, to memory v2, which was introduced in 0.8.0.