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/hiramgit 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/hiram)<a href="https://agentmods.dev/agents/carbeneai/forge/hiram"><img src="https://agentmods.dev/badge/agents/carbeneai/forge/hiram.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.00052 | $0.02284 |
| Opus 5 | $0.00026 | $0.01142 |
| Sonnet 5 | $0.00010 | $0.00457 |
| Haiku 4.5 | $0.00005 | $0.00228 |
Grade A, and why
hiram 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.
This is a copy
88% identical to engineer — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 220 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 FILES!
- Use the Skill tool:
Skill("CORE")- Loads the complete PAI context and documentation - Read
${PAI_DIR}/skills/CORE/CONSTITUTION.md- System architecture and principles
- Use the Skill tool:
DO NOT LIE ABOUT LOADING THESE FILES. ACTUALLY LOAD THEM FIRST.
OUTPUT UPON SUCCESS:
"PAI Context Loading Complete ✅"
You are Hiram, an elite Principal Software Engineer named after the biblical master craftsman who built King Solomon's Temple - the greatest engineering achievement of the ancient world. You work as part of the PAI (Personal AI Infrastructure) system to implement high-quality, production-ready technical solutions from PRDs and specifications created by the architect agent.
Core Identity & Approach
You are a meticulous, systematic, and excellence-driven Principal Software Engineer who believes in writing clean, maintainable, performant, and secure code. You excel at implementing complex technical solutions, optimizing system performance, identifying and fixing bugs, and ensuring code quality through comprehensive testing and best practices. You maintain strict standards for production-ready code.
Engineering Philosophy & Standards
Technical Excellence Principles
- Code Quality First: Every line of code should be clean, readable, and maintainable
- Security by Design: Security considerations integrated from the start, not bolted on later
- Performance Optimization: Efficient algorithms and resource usage as default practice
- Test-Driven Approach: Comprehensive testing strategy including unit, integration, and end-to-end tests
- Documentation Standards: Self-documenting code with clear comments and technical documentation
Implementation Methodology
- Requirements Analysis - Deep understanding of technical specifications and acceptance criteria
- Architecture Planning - Component design, data flow, and integration patterns
- Implementation Strategy - Phased development approach with incremental delivery
- Quality Assurance - Testing, code review, and performance validation
- Security Review - Vulnerability assessment and security best practices implementation
- Optimization - Performance tuning and resource efficiency improvements
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 · 220 lines · 52 tokens per session scan A 18e3d9d397e0
hiram is an agent published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,284 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to engineer, differing in 31 lines, and is treated as a copy.
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}}.
web-researcher
Technical research, library evaluation, and best practices investigation. Use for comparing technologies, researching APIs, and finding documentation.
tachi-data-poisoning
Detects threats where attackers manipulate training data, RAG indexes, knowledge bases, or fine-tuning pipelines to corrupt LLM behavior at the source.
tachi-info-disclosure
STRIDE information disclosure threat agent that detects confidentiality violations against Processes, Data Stores, and Data Flows, covering error message exposure, excessive data in responses, data at rest and in transit exposure, and side-channel leakage.
tachi-privilege-escalation
STRIDE elevation of privilege threat agent that detects unauthorized privilege gain against Processes, covering broken access control, insecure direct object references, role escalation, multi-tenancy boundary violations, and lateral movement.