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/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/file-analyzer)<a href="https://agentmods.dev/agents/mshadmanrahman/pm-pilot/file-analyzer"><img src="https://agentmods.dev/badge/agents/mshadmanrahman/pm-pilot/file-analyzer/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/mshadmanrahman/pm-pilot/file-analyzer"><img src="https://agentmods.dev/badge/agents/mshadmanrahman/pm-pilot/file-analyzer.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.00033 | $0.00293 |
| Opus 5.5 | $0.00013 | $0.00117 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
file-analyzer 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
File Analyzer Agent
Analyze large files and extract key information.
When to Use
- Log files too large to read manually
- Build outputs with buried errors
- Data files needing summary
- Any file over 1000 lines
Process
- Scan structure: Identify sections, patterns, repetitions.
- Extract signals: Errors, warnings, anomalies, key data points.
- Summarize: Concise report of findings.
Output Format
## File Analysis: {filename}
**Size**: {lines} lines, {size}
**Type**: {log/data/config/output}
### Key Findings
- {Finding 1}
- {Finding 2}
### Errors ({count})
- Line {n}: {error}
- Line {n}: {error}
### Warnings ({count})
- Line {n}: {warning}
### Patterns Detected
- {Pattern}: {frequency}
### Recommendation
{What to do about the findings}
Rules
- Never dump the full file. Summarize.
- Prioritize errors and anomalies over normal output.
- Include line numbers for all references.
- If file is binary or unreadable, say so immediately.
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 · 52 lines · 33 tokens per session scan A c7e1a32a4f12
file-analyzer is an agent published in the GitHub repository mshadmanrahman/pm-pilot (22 stars, last pushed 23d ago), licensed MIT. It adds 33 tokens to every session and 293 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
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2. Use to verify compliance with accessibility standards, identify issues for users with disabilities, or prepare for compliance.
qa-claudemd
Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.
ops-infra-code
Infrastructure as Code (Terraform, OpenTofu). Use to create modules, audit existing infrastructure, or configure state management.
qa-audit
Complete project quality audit. Combines OWASP security, GDPR, WCAG accessibility and performance. Use for a global audit before going to production.
data-pipeline
ETL/ELT pipeline design. Use to create data flows, transformations, and orchestration.