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 shopwareLabs/ai-coding-tools --skill ci-log-interpretationgit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/ci-log-interpretation)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/ci-log-interpretation"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/ci-log-interpretation/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/shopwarelabs/ai-coding-tools/ci-log-interpretation"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/ci-log-interpretation.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.00154 | $0.00908 |
| Opus 5.5 | $0.00062 | $0.00363 |
| Sonnet 5.5 | $0.00031 | $0.00182 |
| Haiku 4.5 | $0.00015 | $0.00091 |
Grade A, and why
ci-log-interpretation 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Log Interpretation
Job Name → Tool Mapping
| Job name pattern | Tool |
|---|---|
PHPUnit |
PHPUnit |
PHP analysis / PHPStan |
PHPStan |
PHP lint / ECS / php-cs-fixer |
ECS |
lint (in admin/storefront workflow) |
ESLint, tsc, Stylelint, or Prettier |
Jest / unit (JS context) |
Jest |
acceptance / Playwright |
Playwright |
Lighthouse |
Lighthouse |
Twig Lint / ludtwig |
ludtwig |
Output Signatures
When the job name is ambiguous, identify the tool from its output:
| Signature in log | Tool |
|---|---|
There was 1 failure: or There were N errors: |
PHPUnit |
[ERROR] Found N errors |
PHPStan |
Found N of M files that can be fixed |
ECS |
✖ N problems (N errors, N warnings) |
ESLint |
error TS followed by 4-digit code |
TypeScript (tsc) |
✖ N problems in SCSS context |
Stylelint |
Code style issues found |
Prettier |
● suite-name › test-name |
Jest |
expect(locator).toXxx() failed |
Playwright |
Assertion failed. Exiting with status code 1. |
Lighthouse |
error[RuleName]: |
ludtwig |
Universal Noise (Never the Root Cause)
These patterns appear in ALL GitHub Actions logs and are never the actual error:
- Timestamp prefix: Every line starts with
YYYY-MM-DDTHH:MM:SS.NNNNNNNZ— ignore it - Step boundaries:
##[group]Step Name/##[endgroup]— structural, not errors - Step exit marker:
##[error]Process completed with exit code N.— ALWAYS the last line of a failed step. This is the step exit marker, NOT the actual error. Never report this as the root cause. - Setup noise: checkout, Docker pulls,
actions/cache, composer install, npm install, tool downloads - Post-job noise: cache saving, git config cleanup, orphan process termination
- Infrastructure noise:
npm error command failed,socket hang up,ECONNREFUSED— CI environment issues, not code errors (exception: for Playwright these CAN be the actual cause)
For detailed GitHub Actions log format knowledge, see references/log-envelope.md.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 70 lines · 154 tokens per session scan A 9d27ad0bf41e
ci-log-interpretation is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 7d ago), licensed MIT. It adds 154 tokens to every session and 908 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
ai-diagnostic
A diagnostic framework that examines a problem across technology, processes, people, and business causes.
configure-sentry
Sentry error tracking setup. Use when installing the Sentry SDK, fixing hardcoded DSNs, or adding source map upload for frontend, Next.js, Node, or Python.
crashlytics
Generate crash reports from Firebase Crashlytics with automated fix proposals, severity scoring, and developer assignments via git blame. Use when analyzing crashes, triaging production issues, or generating crash triage reports.
audit-dead-code
Read-only hunt for dead and unused code across four labeled lanes (Knip for TS/JS, vulture for Python, gopls for Go, grep for shell and files no lane owns), each candidate adjudicated dead, uncertain or alive. Use when asked to 'find dead code', to find what is unused in a repository (exports, functions, orphaned…
devils-advocate
Stress-test plans and proposals via systematic adversarial review. Assumption extraction, evidence check, failure scenarios, operational gotchas. Before implementation begins. Use when: asked to attack a plan or proposal ('devil's advocate', 'stress test', 'poke holes', 'what could go wrong'), or before implementation…
known-issues
Lookup and tracking of known Claude product issues: GitHub bug search, service health and model quality checks, and a persistent registry of tracked issues. Use when: 'is this broken', 'any workarounds', 'troubleshoot Claude Code', 'feature behaves unexpectedly', 'scan repo for issues', 'file a bug'. Actions: status…