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/whiteboardmonk/agcluster-container/agents-mdgit clone --depth 1 https://github.com/whiteboardmonk/agcluster-containerWrote 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/instructions/whiteboardmonk/agcluster-container/agents-md)<a href="https://agentmods.dev/instructions/whiteboardmonk/agcluster-container/agents-md"><img src="https://agentmods.dev/badge/instructions/whiteboardmonk/agcluster-container/agents-md.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.00715 | $0.00715 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
agcluster-container 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 5d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Modules
src/agcluster/container/– FastAPI backend:api/endpoints,core/orchestration (session, container, translation),models/Pydantic schemas, andui/Next.js dashboard.tests/– Pytest suites split intounit/andintegration/; markers also covere2e(Docker-backed).e2e/agcluster.spec.ts– Root Playwright checks against a running stack.docker/,docker-compose.yml,configs/,.env.example– Deployment assets; copy.env.exampleto.envbefore local runs.docs/,examples/– Reference material and sample agent configurations.
Build, Test, and Development Commands
- Backend setup:
pip install -e ".[dev]"(Python 3.11+). Start stack:docker compose up -d; rebuild images withdocker compose build. - API-only run (dev):
uvicorn agcluster.container.api.main:app --reloadafter settingANTHROPIC_API_KEYand other env vars. - Backend tests:
pytest tests/(all),pytest tests/unit,pytest tests/integration, orpytest --cov=agcluster.container tests/. - UI workspace (
src/agcluster/container/ui):npm install, thennpm run devfor Next.js,npm run build/npm startfor production,npm testfor Vitest,npm run test:e2efor Playwright UI flows. - Root Playwright smoke (if stack is up):
npm testfrom repo root runsplaywright test.
Coding Style & Naming Conventions
- Python: Black and Ruff with 100-char lines; optional mypy (
mypy src/agcluster). Prefer typed function signatures in new code. - Tests: filenames
test_*.py; classesTest*; functionstest_*. Use pytest markers@pytest.mark.unit|integration|e2eand keep fixtures intests/conftest.py. - TypeScript/React: ESLint + TypeScript; follow existing component patterns in
src/agcluster/container/ui. Use PascalCase for components, camelCase for hooks/utilities. - Tailwind is locked to v3; avoid
@applyin new styles—prefer utility classes or scoped CSS modules.
Testing Guidelines
- Add unit tests for new services/models; integration tests for API surface changes; Playwright for end-to-end UI/agent flows.
- Aim to keep coverage gaps small (HTML report in
htmlcov/frompytest --cov). Include edge cases around Docker/session lifecycle and file handling. - For UI changes, pair Vitest component coverage with Playwright scenarios that validate auth, upload/download, and agent launch flows.
- Record any required Docker/ENV prerequisites in the test description to keep CI reproducible.
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.
- 5d ago First seen · 33 lines · 715 tokens per session scan A 1cfb999a2460
agcluster-container AGENTS.md is an instructions file published in the GitHub repository whiteboardmonk/agcluster-container (77 stars, last pushed 9mo ago), licensed MIT. It adds 715 tokens to every session, about $0.0036 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-30.
Other instructions, from other repositories
SeekMoney-ai CLAUDE.md
Claude Code instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
claude-sessions CLAUDE.md
Instructions for gapmiss/claude-sessions, covering claude sessions — obsidian plugin, development, file structure, code exploration (cymbal) and conventions.
embedded-systems-architect AGENTS.md
Instructions for Zachariah9420/embedded-systems-architect: This repository ships an agent skill for embedded-systems and edge-AI development work.
delphi-spec-kit AGENTS.md
Instructions for delphicleancode/delphi-spec-kit, covering delphi ai spec-kit — agents.md, language and stack, naming conventions — pascal guide, general rule and mandatory prefixes.
contexture AGENTS.md
AGENTS.md instructions for AcKeskin/contexture, covering agents.md, stance (how to engage), commands, testing and project structure.