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 agentmods add skills/event4u-app/agent-config/check-refsnpx skills add event4u-app/agent-config --skill check-refsgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/check-refs)<a href="https://agentmods.dev/skills/event4u-app/agent-config/check-refs"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/check-refs.svg" alt="Measured on agentmods" 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.00035 | $0.00974 |
| Opus 5 | $0.00017 | $0.00487 |
| Sonnet 5 | $0.00007 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
check-refs 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 6d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
check-refs
When to use
Use this skill when:
- A skill, rule, command, guideline, or context has been renamed or deleted
- Linking a newly added artifact from elsewhere in
src/ - Preparing a PR that touches cross-references between agent artifacts
- CI's
check-refsjob failed and the broken reference needs to be located
Do NOT use when:
- Only the body of a single file changed and no names or paths were touched
- Checking frontmatter shape or required sections — use
lint-skillsinstead - Verifying condensed vs uncondensed pairs — use
bash scripts/condense.sh --checkinstead
Procedure
1. Inspect the scope of recent changes
Identify whether any artifact was renamed, moved, or removed since the last clean run. Cross-reference checks are relevant only when names or paths shift; pure body edits cannot break references.
2. Dispatch via the runtime layer
Invoke the skill through the runtime dispatcher so the execution: block in
this skill's frontmatter governs the call:
./scripts-run src/scripts/runtime_dispatcher run --skill check-refs
The dispatcher resolves the request, the shell handler runs
./scripts-run src/scripts/check_references, captures stdout/stderr, and returns a
typed ExecutionResult.
3. Verify the result
Check the returned ExecutionResult:
exit_code: 0→ all cross-references resolveexit_code: 1→ at least one broken reference — readstdoutfor file, line, and the offending ref, then fix the source or update the targetstatus: timeout→ the checker exceededtimeout_seconds— investigatestatus: error→ runner or script missing — confirm./scripts-runandsrc/scripts/check_references.tsare available at the repository root
Output format
- One-line summary:
success | failure | timeout | error, exit code, duration in milliseconds - Count of broken references found, if any
- First 10 broken references with
file:line → missing-target - Next action: fix references, re-run the skill, or surface
stdoutfor review
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.
- 6d ago First seen · 108 lines · 35 tokens per session scan A 352b9e400a54
check-refs is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 974 once invoked, about $0.0002 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
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Concurrency Testing Patterns
Testing concurrent code including race condition detection, deadlock prevention, thread safety verification, and parallel execution correctness.
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.