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 tikalk/adlc-team-skills --skill team-diagnosegit clone --depth 1 https://github.com/tikalk/adlc-team-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/tikalk/adlc-team-skills/team-diagnose)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/team-diagnose"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-diagnose/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/tikalk/adlc-team-skills/team-diagnose"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-diagnose.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.00051 | $0.00789 |
| Opus 5.5 | $0.00020 | $0.00316 |
| Sonnet 5.5 | $0.00010 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
team-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 10d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team-diagnose
Overview
Evidence-first diagnosis of broken adlc-team-skills wiring. The chain has exactly five links, each checkable with one command — a diagnosis without command output is a guess, and guesses get pasted into bug reports.
Boundary: this repo owns .events.json and the boot scripts' output.
The injection side (dispatchers, generated per-agent plugins) is owned by
adlc-cli — the
docs/event-hook-contract.md file in the adlc-team-skills repo draws the
line. Diagnose up to it, then route.
When to Use
- Team context missing at session start (no
Team Context & Decisionssection). - A rule that should have matched didn't load.
- Install behaves unexpectedly after an update.
When NOT to use: for application bugs unrelated to the team-context chain, or for skill behavior debates (that's a goldset/eval question).
Core Process
Run the checks in order — stop at the first failure, fix, re-run:
| # | Symptom area | Check (run it) | Green means |
|---|---|---|---|
| 1 | Not configured | cat .adlc/init-options.json |
A team_ai_directives path that exists |
| 2 | Missing tool | command -v jq |
jq on PATH (skills registry needs it) |
| 3 | Broken handler | bash .agents/skills/team-boot/scripts/boot.sh from the project root |
The directives index on stdout, wrapped in EXTREMELY_IMPORTANT |
| 4 | Stale install | pytest tests/unit/test_generated_artifacts_sync.py -q (in the skills repo) or compare skills/**/SKILL.md vs .agents/skills/ names |
Mirror matches source |
| 5 | Injection side | Generated plugin present and loaded for the agent? | If 1–4 are green and the session still lacks context → adlc-cli's territory — file there with the outputs of checks 1–4 attached |
For "a rule didn't load" specifically: confirm the session began with the index (check 3's content), then check the task actually matched the rule's descriptor — on-demand pull is match-driven, not mind-reading.
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.
- 10d ago Changed 5b2f3f6aa9ce
- 23d ago First seen · 71 lines · 51 tokens per session scan A def62d342665
team-diagnose is a skill published in the GitHub repository tikalk/adlc-team-skills (141 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 789 once invoked, about $0.0002 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-09-23.
Other skills, from other repositories
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
anti-entropy-governance
Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.
agent-debug-fixer
A Chinese-language debugging and repair workflow for software problems. It investigates errors, failed tests, broken pages, or behavior that does not match expectations, then makes a minimal fix.
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.
investigate
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…