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/rpraharaj/forward-deployed-engineer/ci-forensicsnpx skills add rpraharaj/forward-deployed-engineer --skill ci-forensicsgit clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineerWrote 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/rpraharaj/forward-deployed-engineer/ci-forensics)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/ci-forensics"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/ci-forensics.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.00111 | $0.02214 |
| Opus 5 | $0.00056 | $0.01107 |
| Sonnet 5 | $0.00022 | $0.00443 |
| Haiku 4.5 | $0.00011 | $0.00221 |
Grade A, and why
ci-forensics 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI forensics
Getting the pipeline back to meaning something.
Why this exists
A flaky pipeline is worse than no pipeline. Once "just re-run it" becomes the standard response to a red build, the suite has stopped being a signal — and the genuine failure it eventually catches gets re-run away like all the others.
Teams reach this state gradually and rarely climb out, because each individual re-run is cheaper than each individual investigation. The economics only look right locally.
An FDE lands in this often, and has a specific advantage: no accumulated tolerance for it. You haven't learned which failures to ignore, which means you notice that the team has learned to ignore them.
The main discipline is diagnosing the class of failure before fixing anything. The classes look identical from the outside — a red build — and have completely different causes and fixes.
When this applies
- The build is failing and the cause isn't obvious
- Tests pass locally, fail in CI
- Intermittent red builds
- The pipeline is too slow to be useful
- "Just re-run it" has become normal
When it doesn't
- A single obvious failure with a clear cause — just fix it
- Production is broken — that's
incident-triage - You need to build a pipeline that doesn't exist yet
Prerequisites
- Locate the workspace:
FDE_WORKSPACE, else the charter Location, else.fde/, else../<repo>-fde/ .fde/01-environment.md— a working local build, so you can compare against CI- Access to CI logs and history. Build history is the primary evidence here.
Procedure
1. Classify the failure before fixing anything
Five classes. They present identically and have nothing else in common.
| Class | Signature | Fix direction |
|---|---|---|
| Genuine break | Fails consistently, same point, correlates with a change | Fix the code |
| Flake | Same commit passes and fails | Find the nondeterminism |
| Environment drift | Passes locally, fails in CI; or worked last week | Align the environments |
| Ordering dependency | Fails only in some run orders or in parallel | Isolate the shared state |
| Resource contention | Fails under load; timeouts; more common on busy days | Resource limits |
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 · 182 lines · 111 tokens per session scan A da282420fd89
ci-forensics is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 19d ago), licensed MIT. It adds 111 tokens to every session and 2,214 once invoked, about $0.0006 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
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
azdo-build-investigator
Investigate CI failures for dotnet/maui PRs and the nightly/official signed build — build errors, Helix test logs, and binlog analysis. Use when asked about failing checks, CI status, test failures, 'why is CI red', 'build failed', 'what's failing on PR', 'is this PR ready to merge', Helix failures, device test…
fix-ci
Check CI status, analyze test failures, auto-fix obvious issues or discuss with user.
ci-fix
Common safety and triage protocol for .NET MAUI CI-fixer workflows. Use whenever investigating, creating, or advancing a [ci-fix] or [ci-fix-net11] pull request from a ci-scan issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps.
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 when it should be cached, or when outputs are empty or missing after a…