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 event4u-app/agent-config --skill lint-skillsgit 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/lint-skills)<a href="https://agentmods.dev/skills/event4u-app/agent-config/lint-skills"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/lint-skills/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/event4u-app/agent-config/lint-skills"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/lint-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00900 |
| Opus 5 | $0.00015 | $0.00450 |
| Sonnet 5 | $0.00006 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
lint-skills scanned grade A with 1 finding 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
`subprocess.run` with `shell=False`; only argv form is supported How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lint-skills
When to use
Use this skill when:
- Validating the shape of every skill and rule in
src/ - Verifying execution metadata (
execution.type,handler,command) is well-formed - Checking locally before opening a PR that CI's skill-lint job will pass
- Investigating a reported linter failure on a specific skill or rule
Do NOT use when:
- Linting only one file — call
./scripts-run src/scripts/skill_linter <path>directly - Checking cross-references between files — use
check-refsinstead - Checking condensation freshness — use
bash scripts/condense.sh --checkinstead
Procedure
1. Inspect the environment
Confirm ./scripts-run is executable and the working directory is the agent-config
repository root — the linter expects to find src/skills/
and related directories relative to cwd.
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 lint-skills
The dispatcher resolves the request, the shell handler runs
./scripts-run src/scripts/skill_linter --all, captures stdout/stderr, and returns
a typed ExecutionResult.
3. Verify the result
Check the returned ExecutionResult:
status: successandexit_code: 0→ all skills and rules are cleanexit_code: 1→ warnings only — reviewstdoutfor the listed warningsexit_code: 2→ errors present — fix the flagged files before continuingstatus: timeout→ the linter exceededtimeout_seconds— investigatestatus: error→ the runner could not launch — check that./scripts-runis onPATHand the repository root is the current working directory
Output format
- One-line summary:
success | failure | timeout | error, exit code, duration in milliseconds - Count of skills and rules the linter inspected, if known
- List of files with errors (first 10), each with code and message
- Next action: fix errors, re-run, or surface the raw
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.
- 8d ago First seen · 104 lines · 30 tokens per session scan A 2a5eb01dc445
lint-skills is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 900 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
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.
monte-carlo-performance-diagnosis
Diagnoses pipeline performance issues -- slow jobs, expensive queries, latency trends -- using Monte Carlo's cross-platform observability. Uses a tiered investigation approach: discover problems, bridge to affected tables, then drill into root causes. Activates when a user asks about slow pipelines, expensive queries…