Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JimmyPaolini/codebasenpx agentmods add skills/jimmypaolini/codebase/triage-integrationWrote 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/jimmypaolini/codebase/triage-integration)<a href="https://agentmods.dev/skills/jimmypaolini/codebase/triage-integration"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/triage-integration/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/jimmypaolini/codebase/triage-integration"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/triage-integration.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.00097 | $0.08179 |
| Opus 5.5 | $0.00039 | $0.03272 |
| Sonnet 5.5 | $0.00019 | $0.01636 |
| Haiku 4.5 | $0.00010 | $0.00818 |
Grade A, and why
triage-integration 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 25d 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Integration Failures
Diagnose failing integration checks in this codebase—whether they occur locally during git commit / git push or remotely in GitHub Actions CI workflows. Map errors to their root causes, read the relevant configuration, apply targeted fixes, and verify locally.
When to Use
- A
git commitorgit pushis rejected by a local hook (Husky, lint-staged, commitlint, validate-branch-name). - A CI check is red on a pull request or push.
- The user pastes error logs and asks for a fix.
- Asked to "fix CI", "debug the failing check", or "triage submission errors".
Step 1: Obtain the Logs
Determine if this is a local failure or a CI failure.
Option A: Local Submission Failure
NX_PERF_LOGGING=false lint-staged --config configuration/lint-staged.config.ts --continue-on-error
Invoked directly rather than through nx run codebase:lint-staged. That target's own command
still carries NODE_OPTIONS='--import=tsx', which the hook deliberately drops: the flag is
inherited by every command lint-staged runs, and its --import=tsx loader preempts the
transpiler Nx uses for workspace plugins. esbuild emits no design:paramtypes, so the
conformetry plugin's NestJS constructor injection would silently resolve to undefined and the
project graph would fail to build. Node reads the TypeScript config natively instead. The hook
also measures code (nx run codebase:codometer:write) and clears staged notepad files before
running lint-staged.
lint-staged config: configuration/lint-staged.config.ts
Almost every check reaches the staged files through one nx affected run over the
lint-code target:
nx affected --target=lint-code --configuration=check --parallel=8 --outputStyle=static --files=<path> --files=<path> …
One --files= flag per staged path, never one comma-separated value: Node is
killed by the operating system on a single argument past 1011 bytes, and
lint-staged reports that as Task failed to spawn: undefined with no output.
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.
- 25d ago Changed · +220 lines 3c6dc1fbb46f
- 26d ago First seen · 336 lines · 97 tokens per session scan A d35f7b9eb874
triage-integration is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed 18d ago), licensed MIT. It adds 97 tokens to every session and 8,179 once invoked, about $0.0004 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-20.
Other skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
tracely
Instrument AI agents with Tracely and turn their production traces into CI gates. Use when the user mentions Tracely, tracely-ai, tracelysdk, the tracely CLI, or asks to trace/observe an AI agent, add LLM evaluators or LLM-as-a-judge columns, debug why a trace or conversation isn't showing up, wire agent regression…