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 perniemann/pnCore --skill pn-ci-fixgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-ci-fix)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-ci-fix"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-ci-fix/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/perniemann/pncore/pn-ci-fix"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-ci-fix.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.00038 | $0.00258 |
| Opus 5 | $0.00019 | $0.00129 |
| Sonnet 5 | $0.00008 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
pn-ci-fix 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 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.
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.
What it actually says
Fix CI
When to use
- Branch CI is failing and you want a fast, iterative path to green checks.
- You need targeted, minimal fixes applied one failure at a time (diagnosis-only → use pn-ci-triage instead).
- CI is red after a merge, rebase, or dependency bump and needs to be unblocked quickly.
Workflow
- Identify the latest run for the current branch.
- Inspect failed jobs and extract the first actionable error.
- Apply the smallest safe fix.
- Re-run CI and repeat until green.
Guardrails
- Fix one actionable failure at a time.
- Prefer minimal, low-risk changes before broader refactors.
Output
- Primary failing job and root error
- Fixes applied in iteration order
- Current CI status and next action
Guardrails
- pn-ci-triage — Use when the user wants diagnosis and suggestions only ("why did CI fail?"). Use pn-ci-fix when the user wants iterative fixes until green.
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 · 35 lines · 38 tokens per session scan A ad7aed6febd1
pn-ci-fix is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 6d ago), licensed MIT. It adds 38 tokens to every session and 258 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
secrets-management
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
typescript
TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.