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 Bilal140202/the-lord-of-the-skills --skill seemseam__claude_codex_bridgegit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/seemseam__claude_codex_bridge)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/seemseam__claude_codex_bridge"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/seemseam__claude_codex_bridge/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/bilal140202/the-lord-of-the-skills/seemseam__claude_codex_bridge"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/seemseam__claude_codex_bridge.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.00075 | $0.00991 |
| Opus 5 | $0.00037 | $0.00495 |
| Sonnet 5 | $0.00015 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
ccb-self-diagnose 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 12d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCB Self Diagnose
Use this skill for read-only triage. Prefer CCB control-plane diagnostics and read-only tmux evidence. Do not mutate runtime state from this skill.
Evidence Model
Keep these categories separate in every diagnosis:
- Authority: current mounted daemon service graph, lifecycle, lease, current configured-agent runtime records, and loaded config.
- Evidence:
ccb ping,ccb doctor,ccb ps,ccb queue,ccb pend,ccb trace,ccb fault list,ccb doctor logs <agent>, reply/artifact records, tmux pane metadata/text capture, provider session files, pid files, and config validation or reload dry-run output. - Residue: disk-only
.ccb/agents/*directories for unknown agents, stale panes, stale sockets, old session artifacts, dead helpers, and orphaned provider state.
Configured-agent and restart target authority comes from the mounted daemon
graph, not disk config, tmux panes, or .ccb/agents/* residue.
Core Workflow
- Confirm the project anchor and current mounted daemon generation.
- Gather the control-plane snapshot:
ccb ping ccbdccb doctorccb psccb queue --detail allccb fault listccb pend --inbox --detail <agent>when one agent is suspectedccb trace <job_id|message_id|attempt_id|reply_id>for lineage issuesccb doctor logs <agent>when provider/API evidence is needed
- Gather read-only tmux evidence when pane or provider state matters:
- current CCB tmux namespace/session/socket
- pane ids, active/dead flags, titles, current commands, and captured text
- activity sampling when supported
- provider session and pid-file paths plus modification times when useful, without reading secret or private provider-state contents
- For config drift, run
ccb config validatefirst, thenccb reload --dry-run. Do not treat disk config as live graph until reload has succeeded and the daemon graph has been rechecked. - For artifact-backed replies or requests, read the full artifact file before acting. If the full file is absent or expired, report a blocker and do not infer from preview text alone.
- Classify the failure domain and hand off:
- daemon lifecycle, namespace, pane, provider context, config drift, or
storage boundary ->
ccb-self-recover - job/message/reply/artifact/callback lineage ->
ccb-self-chain - config design/edit/reload readiness -> built-in
ccb-config
- daemon lifecycle, namespace, pane, provider context, config drift, or
storage boundary ->
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.
- 12d ago First seen · 101 lines · 75 tokens per session scan A 02670718d5c9
ccb-self-diagnose is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 75 tokens to every session and 991 once invoked, about $0.0004 per session on Opus 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
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
detecting-process-injection-techniques
Detects and analyzes process injection techniques used by malware including classic DLL injection, process hollowing, APC injection, thread hijacking, and reflective loading. Uses memory forensics, API monitoring, and behavioral analysis to identify injection artifacts. Activates for requests involving process…
ainb-fleet:daemon
Long-running watcher that scans every claude session every 5s and auto-sends continue to any session whose recent tmux pane buffer matches a known API-error regex (ratelimited, overloadederror, internalservererror, requesttimeout, sockethangup, fetchfailed, ECONNRESET). Use this when you want unattended recovery from…
investigating-ransomware-attack-artifacts
Identify, collect, and analyze ransomware attack artifacts to determine the variant, initial access vector, encryption scope, and recovery options.
cline-fix-volatile-msg
Ladder-aware Cline Anthropic caching — verify the rolling read/write ladder on the wire, then add the tools breakpoint and tune TTL. Updated for the 2026-08 AI-SDK monorepo.
opencode-detect-openai-compat
OpenCode's caching detection misses OpenAI-compatible proxies routing to Anthropic/Bedrock. Broaden the predicate.