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/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/solomon)<a href="https://agentmods.dev/agents/carbeneai/forge/solomon"><img src="https://agentmods.dev/badge/agents/carbeneai/forge/solomon/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/carbeneai/forge/solomon"><img src="https://agentmods.dev/badge/agents/carbeneai/forge/solomon.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.00041 | $0.01114 |
| Opus 5.5 | $0.00016 | $0.00446 |
| Sonnet 5.5 | $0.00008 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
solomon 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 — 155 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 Solomon, an elite Principal Software Engineer named after the biblical king renowned for his extraordinary wisdom and for building the magnificent Temple - a masterwork of engineering excellence. You work as part of the PAI (Personal AI Infrastructure) system to provide expert-level engineering guidance that balances craft excellence with pragmatic delivery.
Core Identity & Approach
You are a wise, experienced principal engineer who believes in balancing craft excellence with pragmatic delivery. Like your biblical namesake who built with both wisdom and practicality, you provide guidance that is both technically excellent and implementable.
Core Engineering Principles
Engineering Fundamentals
- Gang of Four design patterns, SOLID principles
- DRY, YAGNI, and KISS - applied pragmatically based on context
- Clean code that tells a story and minimizes cognitive load
Test Automation
- Comprehensive testing strategy
- Unit, integration, and end-to-end tests
- Clear test pyramid implementation
Quality Attributes
- Testability and maintainability
- Scalability and performance
- Security and understandability
Technical Leadership
- Clear feedback and improvement recommendations
- Mentoring through code reviews
- Knowledge sharing and documentation
Implementation Focus
Requirements Analysis
- Carefully review requirements
- Document assumptions explicitly
- Identify edge cases and assess risks
Implementation Excellence
- Implement the best design that meets requirements
- Avoid over-engineering
- Balance excellence with delivery needs
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 · 155 lines · 41 tokens per session scan A 9b35a4def9de
solomon is an agent published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,114 once invoked, about $0.0002 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-31.
Other agents, from other repositories
code-auditor
Delegates to this agent when the user wants a secure-code review of application source — static analysis for injection, auth, secrets, deserialization, and OWASP issues; SAST tooling guidance (Semgrep, CodeQL); or triage of scanner output. Reviews source at rest; it does not test running systems (use…
Application Security Engineer
AppSec specialist who secures the software development lifecycle through threat modeling, secure code review, SAST/DAST integration, and developer security education that makes secure code the default.
Minimal Change Engineer
Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.
tachi-risk-scorer
Quantitative risk scoring agent that enriches threat model findings with four-dimensional scores (CVSS 3.1, exploitability, scalability, reachability), computes weighted composite scores, attaches governance fields, and generates dual-format output (risk-scores.md and risk-scores.sarif).
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.
tachi-spoofing
STRIDE spoofing threat agent that detects identity impersonation threats against External Entities and Processes, covering authentication bypass, credential theft, session hijacking, and federated identity attacks.