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/orlojhq/orloj/agentgit clone --depth 1 https://github.com/OrlojHQ/orlojWrote 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/orlojhq/orloj/agent)<a href="https://agentmods.dev/agents/orlojhq/orloj/agent"><img src="https://agentmods.dev/badge/agents/orlojhq/orloj/agent.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.00000 | $0.00705 |
| Opus 5 | $0.00000 | $0.00352 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
agent 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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent
An Agent is a declarative unit of work backed by a language model. It defines what the agent does (its prompt), what model powers it, what tools it can call, and what constraints bound its execution.
Defining an Agent
apiVersion: orloj.dev/v1
kind: Agent
metadata:
name: research-agent
spec:
model_ref: openai-default
prompt: |
You are a research assistant.
Produce concise evidence-backed answers.
tools:
- web_search
- vector_db
memory:
ref: research-memory
roles:
- analyst-role
limits:
max_steps: 6
timeout: 30s
Key Fields
| Field | Description |
|---|---|
model_ref |
Required reference to a ModelEndpoint resource for provider-aware routing. |
prompt |
The system instruction that defines the agent's behavior. |
tools |
List of Tool names this agent may call. Tool calls are subject to governance checks. |
roles |
Bound AgentRole names. Roles carry permissions that authorize tool usage. |
memory.ref |
Reference to a Memory resource. This attaches the memory backend to the agent. |
memory.allow |
Explicit list of built-in memory operations the agent may use: read, write, search, list, ingest. |
limits.max_steps |
Maximum execution steps per task turn. Defaults to 10. |
limits.timeout |
Maximum wall-clock time per task turn. |
How an Agent Executes
When the runtime activates an agent during a task, it:
- Initializes the agent's conversation history with the system prompt and current task context.
- If
memory.refis set, wires the backing memory store into the runtime. Ifmemory.allowis also set, the runtime exposes only those built-in memory operations as available tools. - Routes the request to the configured model via the model gateway, sending the full conversation history.
- If the model selects tool calls, the runtime checks governance (AgentPolicy, AgentRole, ToolPermission) and executes authorized tools. Memory tool calls are handled internally without network calls. Tool results are sent back using the provider's native structured tool protocol (
role: "tool"withtool_call_idfor OpenAI,tool_resultcontent blocks for Anthropic). - Results are appended to the conversation history and sent back to the model for the next step. The agent completes when the model produces text output without requesting further tools, or when
max_steps/timeoutis reached. Already-called tools are removed from the available list to prevent duplicate calls.
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.
- 4d ago First seen · 60 lines · 0 tokens per session scan A 4f17cca9d9ec
agent is an agent published in the GitHub repository OrlojHQ/orloj (117 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 705 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
acx-tester
AgentCortex /test phase executor. Use when delegating test verification that must follow the test skeleton, coverage delta, and evidence requirements per agentic-os governance.
acx-implementer
AgentCortex /implement phase executor. Use when delegating implementation work that must follow agentic-os gates, evidence requirements, and skill injection.
board-workflow
This document describes the end-to-end workflow for AI-assisted issue resolution, from initial issue creation through merged PR.
claude-expression
DISCLAIMER: This document is managed exclusively by Claude Code. The repository admin (AndrewAltimit) does not manage this file and is not allowed to directly edit it. Any updates must come from Claude Code through collaborative sessions.
codebase-analysis-pipeline
This document describes a two-stage automated pipeline for continuous codebase improvement.
guardian
The Guardian is the last line of defense between your code and production. It runs a multi-dimensional quality gate that checks tests, type safety, security, code quality, and documentation coverage in a single pass. Unlike a CI pipeline that tells you something broke 10 minutes after you pushed, the Guardian catches…