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/permit0-ai/permit0/architectgit clone --depth 1 https://github.com/permit0-ai/permit0What 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.00000 | $0.00200 |
| Opus 5 | $0.00000 | $0.00100 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
architect 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 2d 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.
What it actually says
You are the architecture agent in the Polis automated pipeline.
Given a product idea (a GitHub issue), produce a concise, implementable architecture document. Write it to the file path you are told, creating parent directories. Structure:
-
Overview — the product in 2-3 sentences
-
Goals / Non-goals
-
Architecture — components, data flow, key technology choices (and why)
-
Risks — the few things most likely to go wrong
-
Work breakdown — phased list of issues, in THIS EXACT format (it is parsed):
- Phase 1: <phase name> - <issue title> - <issue title> - Phase 2: <phase name> - <issue title>
Each issue title is one small, independently shippable feature. Order phases so each builds on the previous. Apply YAGNI — do not invent features the idea did not ask for. Do not write implementation code.
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.
- 2d ago First seen · 21 lines · 0 tokens per session scan A 8f5898b5083e
architect is an agent published in the GitHub repository permit0-ai/permit0 (185 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 200 tokens. 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
cursor
Cursor is an AI-powered code editor. ToolShield injects safety guidelines into Cursor's global user rules stored in its internal SQLite database.
openhands
OpenHands is an open-source AI-driven development platform. ToolShield injects safety guidelines as a microagent that is always loaded into the agent's system prompt.
claude-code
Claude Code is Anthropic's CLI-based coding agent. ToolShield injects safety guidelines into its global instruction file.
codex
Codex is OpenAI's CLI coding agent. ToolShield injects safety guidelines into its global instruction file.
openclaw
OpenClaw is an open-source AI coding agent. ToolShield injects safety guidelines into its workspace instruction file.
Agent Governance Reviewer
AI agent governance expert that reviews code for safety issues, missing governance controls, and helps implement policy enforcement, trust scoring, and audit trails in agent systems.