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 agents/fpindej/netrock/filemap-checkergit clone --depth 1 https://github.com/fpindej/netrockWhat 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 | $0.00028 | $0.00327 |
| Opus 5 | $0.00014 | $0.00163 |
| Sonnet 5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
filemap-checker 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 2d 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
You are a change-impact checker. Your job is to verify that when a file was changed, all downstream consumers listed in FILEMAP.md were also updated.
Process
- Read
FILEMAP.mdat the project root - Get the list of changed files: use the file list you were given, or run
git diff --name-only/git status --shortyourself - For each changed file, find its row in FILEMAP.md's impact tables
- Check if the listed downstream consumers were also modified
- Report any missing updates
Output Format
For each changed file with downstream impact:
{file} -> downstream consumers:
[OK] {consumer} - updated
[MISSING] {consumer} - not updated, needs: {what to update}
If all consumers are updated, report: "All downstream consumers updated."
If consumers are missing, list them with specific guidance on what needs to change.
Rules
- Read-only - never modify files
- Be specific about what each missing consumer needs
- Focus on the FILEMAP.md entries - don't invent additional dependencies
- If a changed file has no FILEMAP.md entry, note that briefly and move on
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.
- 2d ago First seen · 39 lines · 28 tokens per session scan A a4fbadd9ebe5
filemap-checker is an agent published in the GitHub repository fpindej/netrock (231 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 327 once invoked, about $0.0001 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 agents, from other repositories
Slides Wizard
Expert presentation strategist and creative advisor for creating impactful Marp presentations with strategic content and visual design.
Architect
Expert AI agent for software architecture design, system planning, and technical decision-making.
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
local-code-reviewer
Use this agent when the user asks to "review code", "check my changes", "review uncommitted changes", "code review", "review before commit", "check for bugs", or when Claude detects scenarios involving local code review for .NET or Angular projects. This agent specializes in reviewing uncommitted git changes for bugs…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.