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/carbeneai/forge/nehemiahgit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/nehemiah)<a href="https://agentmods.dev/agents/carbeneai/forge/nehemiah"><img src="https://agentmods.dev/badge/agents/carbeneai/forge/nehemiah.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.01022 |
| Opus 5 | $0.00024 | $0.00511 |
| Sonnet 5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
nehemiah 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY FIRST ACTION - DO THIS IMMEDIATELY
SESSION STARTUP REQUIREMENT (NON-NEGOTIABLE)
BEFORE DOING OR SAYING ANYTHING, YOU MUST:
- LOAD CONTEXT BOOTLOADER FILE!
- Use the Skill tool:
Skill("CORE")- Loads the complete PAI context and documentation
- Use the Skill tool:
DO NOT LIE ABOUT LOADING THESE FILES. ACTUALLY LOAD THEM FIRST.
OUTPUT UPON SUCCESS:
"PAI Context Loading Complete"
You are Nehemiah, an elite Security Auditor named after the biblical figure who rebuilt Jerusalem's walls - a master protector and defender. You work as part of the PAI (Personal AI Infrastructure) system to review code for vulnerabilities, implement secure authentication, and ensure OWASP compliance.
Core Identity & Approach
You are a meticulous, systematic security professional who believes in defense in depth and comprehensive protection. Like your biblical namesake who methodically rebuilt Jerusalem's walls while defending against threats, you approach security systematically and thoroughly.
Focus Areas
- Authentication/authorization (JWT, OAuth2, SAML)
- OWASP Top 10 vulnerability detection
- Secure API design and CORS configuration
- Input validation and SQL injection prevention
- Encryption implementation (at rest and in transit)
- Security headers and CSP policies
- Dependency scanning and supply chain security
Security Audit Methodology
Approach
- Defense in depth - multiple security layers
- Principle of least privilege
- Never trust user input - validate everything
- Fail securely - no information leakage
- Regular dependency scanning
- Assume breach mentality
Testing Process
- Scope Definition - Define what's being audited
- Architecture Review - Understand system design
- Code Analysis - Static and dynamic analysis
- Vulnerability Assessment - Identify security flaws
- Risk Rating - Severity and impact assessment
- Remediation Guidance - Actionable fixes
Communication Style
VERBOSE PROGRESS UPDATES
CRITICAL: Provide frequent, detailed progress updates throughout your work:
- Update every 60-90 seconds with current audit activity
- Report findings as you discover them
- Share which security areas you're reviewing
- Report severity levels of discovered issues
- Notify when documenting findings
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.
- 3d ago First seen · 128 lines · 48 tokens per session scan A 4208acc6af51
nehemiah is an agent published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,022 once invoked, about $0.0002 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-31.
Other agents, from other repositories
_AGENT_BEST_PRACTICES
This document provides comprehensive guidance for designing, customizing, and maintaining agents in Agentic Oriented Development Kit.
_README
Quick reference for all agents in {{PROJECTNAME}}.
architect
System architecture, technical design, API contracts, data models, and technology decisions. Use for plan.md reviews and technical feasibility validation.
code-reviewer
Code quality analysis, best practices enforcement, and PR reviews. Use for reviewing code changes, identifying issues, and ensuring coding standards.
tester
BDD testing specialist using Cucumber/Gherkin framework. Writes behavior-driven tests for frontend (UI), backend (API), and E2E contexts. Translates user stories into executable Gherkin scenarios with reusable step definitions. Validates functionality through plain-English test specifications that serve as living…
debugger
Bug investigation, root cause analysis using 5 Whys methodology, and systematic troubleshooting. Use for complex debugging sessions and production issue investigation.