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-triagegit 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-triage)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-ci-triage"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-ci-triage/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-triage"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-ci-triage.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.00041 | $0.00492 |
| Opus 5 | $0.00020 | $0.00246 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
pn-ci-triage 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
CI triage skill
When to use
- A GitHub Actions or GitLab CI run has failed
- User asks "why did CI fail?" or "how do I fix this CI error?"
- Drafting or updating a workflow and need to reason about steps and dependencies
Workflow
- Locate the failure: Identify which job and which step failed from the CI summary or logs. Note the exact error message and exit code if shown.
- Classify the failure: Common types: (a) test failure (assertion or runtime in tests), (b) lint/format failure, (c) build/compile failure, (d) missing secret or env var, (e) dependency install failure, (f) timeout or resource issue, (g) permission or path issue.
- Suggest a fix: For (a)–(c) point to the file and line if possible and suggest a concrete change or command to run locally. For (d) remind to set the secret/variable in the platform and not in the workflow file. For (e)–(g) suggest platform-specific fixes (e.g. cache key, job timeout, working directory).
- Link to docs: Where helpful, link to the relevant CI docs (e.g. GitHub Actions, GitLab CI) for the failing step or feature.
- Dev/prod staging: When user asks for dev/prod or staging vs production CI setup, recommend pn-ci-dev-prod-split.
- Suggestion only: Frame output as suggestions; the user should apply changes and re-run CI. Do not assume you have full repo or env context.
Output
- Failing job and step, failure type, and suggested fix (with file/line when applicable).
- Links to CI platform docs where helpful.
Guardrails
- pn-ci-fix — Use when the user wants the agent to iteratively fix CI (apply fixes and re-run until green). Use pn-ci-triage for diagnosis and suggestions only.
- pn-ci-dev-prod-split — Use when scaffolding or changing dev/prod or staging workflows.
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 · 32 lines · 41 tokens per session scan A 88e94fcce448
pn-ci-triage is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 492 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.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
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.