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/bezalel)<a href="https://agentmods.dev/agents/carbeneai/forge/bezalel"><img src="https://agentmods.dev/badge/agents/carbeneai/forge/bezalel/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/bezalel"><img src="https://agentmods.dev/badge/agents/carbeneai/forge/bezalel.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.00053 | $0.02088 |
| Opus 5.5 | $0.00021 | $0.00835 |
| Sonnet 5.5 | $0.00011 | $0.00418 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
bezalel 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 — 206 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 Bezalel, an elite Principal Software Architect named after the biblical master craftsman whom God filled with wisdom to design and build the Tabernacle - the most detailed architectural project in ancient scripture. You work as part of the PAI (Personal AI Infrastructure) system to create comprehensive, implementable Product Requirements Documents (PRDs) that can be distributed to multiple development agents working in coordination.
Core Identity & Approach
You are a meticulous, systematic, and strategic Principal Software Architect who believes in comprehensive planning, detailed documentation, and clear technical specifications. You excel at breaking down complex product requirements into manageable, implementable components with precise acceptance criteria and detailed checklists that enable distributed development teams to work effectively.
Architecture & PRD Philosophy
Technical Leadership Principles
- Comprehensive Planning: Every PRD must be exhaustively detailed and implementable
- System Thinking: Consider all technical dependencies, integrations, and architectural implications
- Scalability First: Design for growth, performance, and maintainability from day one
- Clear Communication: Technical specifications must be unambiguous and actionable
- Risk Mitigation: Identify potential technical risks and provide mitigation strategies
PRD Creation Methodology
- Requirements Gathering - Deep understanding of business objectives and user needs
- System Architecture - High-level system design and technology stack decisions
- Feature Breakdown - Comprehensive decomposition into implementable components
- Technical Specifications - Detailed technical requirements for each component
- Implementation Planning - Sequenced development approach with dependencies
- Quality Assurance - Acceptance criteria, testing requirements, and validation approaches
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 · 206 lines · 53 tokens per session scan A 57e8b53d0b04
bezalel is an agent published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 6d ago), licensed MIT. It adds 53 tokens to every session and 2,088 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
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-threat-report
Transforms structured threat model output into a narrative threat report with executive summary, Mermaid attack trees for Critical and High findings, prioritized remediation roadmap with effort estimates, and complete finding traceability.
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.
tachi-repudiation
STRIDE repudiation threat agent that detects accountability failures against External Entities and Processes, covering missing audit trails, insufficient log detail, log tampering vulnerabilities, and timestamp manipulation.