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 fpindej/netrock --skill add-ci-areagit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/add-ci-area)<a href="https://agentmods.dev/skills/fpindej/netrock/add-ci-area"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/add-ci-area/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/fpindej/netrock/add-ci-area"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/add-ci-area.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00008 | $0.00321 |
| Opus 5 | $0.00004 | $0.00161 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
add-ci-area 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 9d 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
Adds a new project area to CI.
Steps
- Open
.github/workflows/ci.yml - Add a path filter in the
changesjob:mobile: - 'src/mobile/**' - Add an output to the
changesjob:mobile: ${{ steps.filter.outputs.mobile }} - Add a new job (copy an existing one and adapt):
mobile-checks: name: Mobile checks needs: changes if: needs.changes.outputs.mobile == 'true' runs-on: ubuntu-latest timeout-minutes: 10 defaults: run: working-directory: src/mobile steps: - uses: actions/checkout@v6 # ... setup + build + lint + test steps - Add the new job to the gate job's
needs:ci-passed: needs: [backend-build, frontend-checks, mobile-checks] - (If the project has a Dockerfile) Add a corresponding job to
.github/workflows/docker.ymland update itson.pathsanddorny/paths-filterfilters - Verify: push a branch and confirm the new job appears in the PR checks
No branch protection changes needed - the CI passed gate job covers all upstream jobs automatically.
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.
- 9d ago First seen · 44 lines · 8 tokens per session scan A b41d3660e986
add-ci-area is a skill published in the GitHub repository fpindej/netrock (232 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 321 once invoked, about $0.0000 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-30.
Other skills, from other repositories
api-design
Guidelines for RESTful API design, endpoint naming conventions, and standardizing JSON responses.
python
Enforces FastAPI, Dependency Injection, and general Python coding standards based on the repository structure.
react
Guidelines for the React frontend, TanStack ecosystem, and React 19 standards. Use when modifying the UI.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
database-management
Standards for SQLAlchemy async models, PostgreSQL indexing, UTC datetimes, and Alembic migrations.