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 instructions/hoja-solutions/agent-stdlib/agents-mdgit clone --depth 1 https://github.com/Hoja-Solutions/agent-stdlibWhat 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.00969 | $0.00969 |
| Opus 5 | $0.00485 | $0.00485 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
agent-stdlib AGENTS.md 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 yesterday.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using agent-stdlib in any harness
This pack ships as a Claude Code plugin, but most of it is not Claude-specific. This file maps each part to its portable form for harnesses like OpenCode, Cursor, Cline, or a custom agent, on any tool-using model.
What ports cleanly
- MCP servers (
mcp-servers/think,tool-gateway,code-execution): MCP is an open protocol, so any MCP client can mount them. See "Mount the MCP servers". - Scripts (
skills/*/scripts/*.py,scripts/locks.py): plain Python, run anywhere. scripts/autonomy_loop.sh: setAGENT_RUNNERto your headless agent CLI (it defaults toclaude -p), e.g.AGENT_RUNNER="opencode run".
What needs re-wrapping
- Skills (
skills/<name>/SKILL.md): the content is harness-neutral; the auto-loading and triggering is a Claude Code feature. Load the file as a rule or paste its body into your system prompt. See "Use the skills as plain content". - hooks (
hooks/): the classification logic in both the action gate and the injection screen is reusable; thehooks.jsonwiring and the input JSON shapes are Claude Code's. See "Port the hooks". - Commands and agent (
commands/,agents/): Claude Code formats that also rely on its subagent dispatch. Reuse the recipe inside them, not the files.
Use the skills as plain content
Every skill is a self-contained markdown procedure. Point your agent at
skills/<name>/SKILL.md, or copy the body into your rules file (AGENTS.md,
.cursorrules, a system prompt). The frontmatter description says when each
skill applies, which is enough for a router to pick one. On a smaller model,
load the one you need explicitly rather than expecting it to self-select.
Mount the MCP servers
The servers speak MCP over stdio and need uv,
which installs each one's single dependency on first run. A vendor-neutral
config most clients accept:
{
"mcpServers": {
"think": {
"command": "uv",
"args": ["run", "/abs/path/agent-stdlib/mcp-servers/think/server.py"]
},
"tool-gateway": {
"command": "uv",
"args": ["run", "/abs/path/agent-stdlib/mcp-servers/tool-gateway/server.py"]
}
}
}
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.
- yesterday First seen · 85 lines · 969 tokens per session scan A 2510a8ac604b
agent-stdlib AGENTS.md is an instructions file published in the GitHub repository Hoja-Solutions/agent-stdlib (1 stars, last pushed 1mo ago), licensed MIT. It adds 969 tokens to every session, about $0.0048 per session on Opus 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 instructions, from other repositories
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
agent-ship CLAUDE.md
Instructions for Agent-Ship/agent-ship, covering claude.md, project overview, commands, docker development (recommended) and local development (no docker).
clawock AGENTS.md
Instructions for KCNyu/clawock, covering agents.md - your workspace, every session, kcn 偏好, git hook (one-time setup per clone) and git auto-commit rules.
agents CLAUDE.md
Instructions for eloylp/agents, covering claude.md, project overview, directory structure, config model and build & run.