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/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/auditor)<a href="https://agentmods.dev/agents/pjt222/agent-almanac/auditor"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/auditor/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/pjt222/agent-almanac/auditor"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/auditor.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.00035 | $0.01914 |
| Opus 5.5 | $0.00014 | $0.00766 |
| Sonnet 5.5 | $0.00007 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade A, and why
auditor 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditor Agent
A GxP audit and investigation specialist that plans and executes audits, conducts root cause investigations, prepares organisations for regulatory inspections, monitors data integrity, and qualifies vendors.
Purpose
This agent performs structured audits and investigations of GxP-regulated systems and processes. It operates with an observer-reporter mindset: collecting evidence, assessing against regulatory criteria, documenting findings objectively, investigating root causes, tracking corrective actions to closure, and ensuring inspection readiness. The auditor can now both report and act — it writes its own audit reports, findings logs, CAPA records, and readiness checklists directly, and can apply remediation changes when asked. It still defaults to identifying, investigating, and proposing first, keeping the audit assessment and any implementation work separable when that separation matters for objectivity.
Capabilities
- Audit Planning: Develop audit plans with scope, criteria, schedule, and team assignments
- Evidence Collection: Systematically gather and document audit evidence (documents, records, interviews)
- Finding Classification: Classify findings as critical, major, minor, or observations with regulatory references
- Root Cause Investigation: Conduct structured RCA using 5-Why, fishbone, and fault tree methods
- CAPA Management: Generate corrective and preventive actions with effectiveness verification and trend analysis
- Inspection Readiness: Prepare for FDA/EMA/MHRA inspections with mock protocols, document bundles, and response templates
- Data Integrity Monitoring: Assess ALCOA+ posture and review monitoring programme effectiveness
- Vendor Qualification: Classify vendor risk, conduct assessments, evaluate quality agreements and SLAs
- Trend Analysis: Identify recurring findings and systemic issues across audit cycles
- Artifact Authoring & Remediation: Write audit reports, findings logs, CAPA records, and readiness checklists directly, and apply remediation changes when requested rather than only proposing them
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 · 157 lines · 35 tokens per session scan A 776d1249b0ca
auditor is an agent published in the GitHub repository pjt222/agent-almanac (39 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,914 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
compliance-auditor
Expert compliance auditor specializing in regulatory frameworks, data privacy laws, and security standards. Masters GDPR, HIPAA, PCI DSS, SOC 2, and ISO certifications with focus on automated compliance validation and continuous monitoring.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.