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 parisgroup-ai/imersao-ia-setup --skill ci-fixgit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/ci-fix)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/ci-fix"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/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/parisgroup-ai/imersao-ia-setup/ci-fix"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/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.00068 | $0.00652 |
| Opus 5 | $0.00034 | $0.00326 |
| Sonnet 5 | $0.00014 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Fix
Diagnose and fix CI failures from the latest workflow run.
Workflow
Step 1: Identify the failure
# Get the latest failed run
gh run list --limit 5 --json databaseId,status,conclusion,name,headSha
Pick the most recent failed run and get logs:
gh run view <run_id> --log-failed 2>&1 | tail -80
Step 2: Classify the failure
| Error Pattern | Category | Fix Strategy |
|---|---|---|
error TS2307: Cannot find module in design-system check |
tsconfig exclusion | Add path to tsconfig.design-system.json exclude |
Markup ownership check failed |
baseline drift | Update count in scripts/architecture/markup-ownership-baseline.json |
Design token catalog out of date |
token sync | Run pnpm tokens:build and commit |
error TS in type-check:src |
type error | Fix the TypeScript error in source |
ESLint found too many warnings |
lint warning | Fix the lint issue (often no-explicit-any or react-hooks/exhaustive-deps) |
Coverage threshold failures |
coverage gap | Add targeted tests for uncovered branches |
E409 Conflict on npm publish |
tag misalignment | Create missing git tag at correct commit |
changelog:validate failure |
changelog format | Fix Keep a Changelog structure |
Step 3: Apply the fix
Fix the issue locally, then verify:
npm run type-check
npm run test:coverage
npm run lint
Step 4: Commit and push
Use fix(ci): commit prefix for CI-only fixes:
git add <fixed-files>
git commit -m "fix(ci): <description of what was fixed>"
git push origin main
Step 5: Monitor the new run
gh run list --limit 2 --json databaseId,status,conclusion,name
gh run watch <new_run_id>
If it fails again, re-run from Step 1 with the new failure logs.
Common Multi-Fix Patterns
Sometimes a single push reveals multiple issues. Fix them all in one commit:
- tsconfig + markup baseline — common when adding new demo pages with new components
- type errors + lint warnings — common when adding
anytypes to bridge props - token sync + changelog — common when theme changes happen
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.
- 11d ago First seen · 74 lines · 68 tokens per session scan A c7277bda300b
ci-fix is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 28d ago), licensed MIT. It adds 68 tokens to every session and 652 once invoked, about $0.0003 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
diagnose-deployment
Surfaces PAC CLI upload errors and Dataverse async operation errors, pattern-matches against a known failure catalog, and optionally auto-fixes identified issues. Use when asked to: "diagnose deployment", "debug deployment", "deployment failed", "show deployment errors", "fix deployment issues", "show upload logs"…
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
architecture-optimization
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer …
remove-technical-debt
Guided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture…
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
squid-review-ci
Drive CI green on a pushed, review-clean feature PR — On-Call diagnoses failures and hands fix tasks to the SWE. Output: a CI-validated feature PR. Trigger after /squid-review passes.