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.
git clone --depth 1 https://github.com/DeevsDeevs/agent-systemWrote 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/commands/deevsdeevs/agent-system/chain-link)<a href="https://agentmods.dev/commands/deevsdeevs/agent-system/chain-link"><img src="https://agentmods.dev/badge/commands/deevsdeevs/agent-system/chain-link/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/commands/deevsdeevs/agent-system/chain-link"><img src="https://agentmods.dev/badge/commands/deevsdeevs/agent-system/chain-link.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.00980 |
| Opus 5.5 | $0.00000 | $0.00392 |
| Sonnet 5.5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
chain-link 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creates a detailed summary of the conversation chunk for continuing work in future sessions.
Chain name: $ARGUMENTS
If no chain name provided, ask the user for one.
Goal
Create a thorough summary capturing technical details, code patterns, architectural decisions, unresolved bugs, and solutions attempted. This enables seamless continuation without losing context.
Process
Before your final summary, wrap analysis in <analysis> tags to organize thoughts. Chronologically analyze each message, identifying:
- User's explicit requests and intents
- Your approach to addressing requests
- Key decisions, technical concepts, code patterns
- Specific details: file names, full code snippets, function signatures, line numbers
- Bugs encountered and solutions attempted (successful and failed)
Your summary should include:
- Primary Request and Intent: Capture all user's explicit requests in detail
- Key Technical Concepts: Technologies, frameworks, and patterns discussed
- Work Completed: What was successfully finished and is working (e.g., "Auth handler fully implemented and tested")
- Decisions and Rationale: Key decisions made (approach A over B) and why
- Files and Code Changes:
- Created: New files with full code
- Modified: Changed files with before/after snippets and line numbers
- Read: Files examined for context (brief note on why)
- Unresolved Issues and Blockers: ONLY unresolved problems with:
- Complete error messages and stack traces
- Symptoms and when discovered
- All solutions attempted (what worked, what didn't, why)
- Current status
- Pending Tasks: Explicitly requested but incomplete tasks
- Current Work: What was in progress when this link was created (file names, line numbers, code snippets)
- Next Step: Immediate next action, directly aligned with user's requests
Create a slug (e.g., implement-auth-handler) and readable summary (e.g., "Implement Auth Handler")
Output Structure
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 · 124 lines · 0 tokens per session scan A bbd5737b6073
chain-link is a command published in the GitHub repository DeevsDeevs/agent-system (41 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 980 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-08-30.
Other commands, from other repositories
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
research
Research a technical or product question.
sprint-plan
Generate or update sprint plan.
tech-debt
Track and prioritize technical debt.
hello-stranger
Say hello stranger.