Borrowing it
Nothing to install: this file belongs to CableZa/codex-self-hosted-web-monitor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CableZa/codex-self-hosted-web-monitor/main/AGENTS.mdgit clone --depth 1 https://github.com/CableZa/codex-self-hosted-web-monitorWrote 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/cableza/codex-self-hosted-web-monitor/agents-md)<a href="https://agentmods.dev/instructions/cableza/codex-self-hosted-web-monitor/agents-md"><img src="https://agentmods.dev/badge/instructions/cableza/codex-self-hosted-web-monitor/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/cableza/codex-self-hosted-web-monitor/agents-md"><img src="https://agentmods.dev/badge/instructions/cableza/codex-self-hosted-web-monitor/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00597 | $0.00597 |
| Opus 5 | $0.00298 | $0.00298 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
codex-self-hosted-web-monitor AGENTS.md scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl http://127.0.0.1:18787/healthz` What it actually says
Repository Notes
- First-run setup guide for new users:
docs/setup.md. - Update
CHANGELOG.mdfor every commit that will be pushed. - Maintained files must stay at or below 700 lines of code, excluding blank and comment-only lines. Ignore
package-lock.json. Runscripts/check-line-limitsbefore committing. - Use Semantic Versioning for release versions and tags, for example package/app version
0.2.0with git tagv0.2.0. - After any post-review edit, run another clean subagent review before committing or amending.
- Verify local git state after subagent activity before trusting a status report.
- For releases, confirm the package/app version, changelog section, commit, and tag all match.
- Pushing workflow files requires GitHub
workflowscope. - Run this app with Docker Compose from the repo root:
docker-compose up --build -d monitor scanner valkey - Windows users who cannot use Docker can run the local scripts from the repo root:
powershell -ExecutionPolicy Bypass -File .\scripts\start-local.ps1and stop with:powershell -ExecutionPolicy Bypass -File .\scripts\stop-local.ps1 - For user updates, prefer
./scripts/update-and-redeploy; for redeploying the current checkout, use./scripts/redeploy, then check/healthz. - The scanner checks remote release tags on a schedule and writes
runtime/update-status.json, which the dashboard exposes through/api/update-status. You can also runpython scripts/update-monitor.py checkmanually. - Use
python scripts/update-monitor.py applyonly from a clean worktree. It runsgit pull --ff-only, then redeploys Docker installs with Docker Compose or restarts local Windows installs with the PowerShell scripts. - Normal deploys must preserve runtime state. Prefer
docker-compose up --build -d ...ordocker-compose restart .... - Local Windows installs store runtime SQLite state in repo-root
monitor.sqlite3; Docker installs store it in themonitor-datavolume. - Do not remove Docker volumes, delete SQLite databases, or run
docker-compose down -vunless the user explicitly asks for a reset and a backup or recovery path has been considered. - Optional startup overrides are documented in
.env.example. - The monitor dashboard must be served at
http://127.0.0.1:18787. - Do not use port
8787directly on the host. Indocker-compose.yml, host port18787maps to container port8787. - Check the running service with:
curl http://127.0.0.1:18787/healthz - The
monitorcontainer serves the production frontend fromstatic/; rebuild with Docker Compose after code or frontend changes.
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.
- 12d ago First seen · 29 lines · 597 tokens per session scan A b3604d41e0f6
codex-self-hosted-web-monitor AGENTS.md is an instructions file published in the GitHub repository CableZa/codex-self-hosted-web-monitor (1 stars, last pushed 2mo ago), licensed MIT. It adds 597 tokens to every session, about $0.0030 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).