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/premhiru/agentcloud/agents-mdgit clone --depth 1 https://github.com/premhiru/agentcloudWhat 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.00317 | $0.00317 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
agentcloud 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.
What it actually says
AgentCloud engineering rules
- Preserve strict tenant isolation: every tenant-owned repository/service operation requires an organization ID.
- Preserve immutable, versioned WorkerSpecs. Never mutate deployed specs or detach runs from their exact version.
- Never bypass the deterministic Policy Engine. Unknown operations are denied by default.
- Never expose credentials in WorkerSpecs, browser bundles, logs, audit events, APIs, or MCP output.
- Keep integrations behind
IntegrationAdapterand runtimes behindWorkerRuntime. - Preserve approval request hashing, side-effect idempotency, and dry-run write suppression.
- Add tests for every security-sensitive change, especially tenant, policy, approval, and write paths.
- Do not add dead UI controls or fake navigation.
- Run lint, typecheck, tests, and production build before declaring work complete.
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices.
This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
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 · 22 lines · 317 tokens per session scan A f6023b0d35c2
agentcloud AGENTS.md is an instructions file published in the GitHub repository premhiru/agentcloud (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 317 tokens to every session, about $0.0016 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
agentfootprint AGENTS.md
Instructions for footprintjs/agentfootprint, covering agentfootprint — agent instructions (openai codex), core thesis, the mental model — three slots, six flavors, mock-first development (recommended workflow) and public api.
asap-protocol AGENTS.md
AGENTS.md instructions for asap-protocol/asap-protocol, covering agents.md, project context, quick start, agent guidance (rules vs skills) and knowledge map.
agentfootprint CLAUDE.md
Instructions for footprintjs/agentfootprint, covering agentfootprint — feature-work map, before you design it: it may already exist, module map, core state & flow and extension points.
agent-leash AGENTS.md
Instructions for tonydzi/agent-leash, covering agents.md — working in this repo, what this repo is, layout, how to verify a change and conventions — the claim discipline.
vikunja-mcp CLAUDE.md
Instructions for ufna/vikunja-mcp, covering claude.md, what this is, commands, architecture and testing philosophy.
lantern AGENTS.md
Instructions for lanseqingling/lantern, covering agents.md, project, commands, repository guide and architecture boundaries.