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.
git 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/agents/fpindej/netrock/filemap-checker)<a href="https://agentmods.dev/agents/fpindej/netrock/filemap-checker"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/filemap-checker/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/agents/fpindej/netrock/filemap-checker"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/filemap-checker.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.00028 | $0.00327 |
| Opus 5.5 | $0.00011 | $0.00131 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 39 lines · 28 tokens per session scan A a4fbadd9ebe5
filemap-checker is an agent published in the GitHub repository fpindej/netrock (234 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 327 once invoked, about $0.0001 per session on Opus 5.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
code-reviewer
Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices.
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
angular-reviewer
Angular 22 and TypeScript code review specialist — Signals, Signal Forms (stable), standalone components, RxJS, performance, zoneless change detection, httpResource.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.
symfony-reviewer
Symfony 8.1 / PHP 8.4+ (8.5 recommended) code review specialist — DDD, Doctrine, CQRS, API Platform.
Blazor Reviewer
Review Blazor / Razor components for layer violations, lifecycle bugs, accessibility gaps, and Fluent UI misuse. Use for PR reviews on .razor / .razor.cs files.