Borrowing it
Nothing to install: this file belongs to r3dz4r/datapulse-my. 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/r3dz4r/datapulse-my/main/AGENTS.mdgit clone --depth 1 https://github.com/r3dz4r/datapulse-myWrote 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/r3dz4r/datapulse-my/agents-md)<a href="https://agentmods.dev/instructions/r3dz4r/datapulse-my/agents-md"><img src="https://agentmods.dev/badge/instructions/r3dz4r/datapulse-my/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.1 | $0.02618 | $0.02618 |
| Opus 5 | $0.01309 | $0.01309 |
| Sonnet 5 | $0.00524 | $0.00524 |
| Haiku 4.5 | $0.00262 | $0.00262 |
Grade A, and why
datapulse-my 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — r3dz4r/datapulse-my
Working agreement for AI agents (Hermes, Codex, Claude Code) operating inside this repository. Read once, then follow on every change.
What this repo is
r3dz4r/datapulse-my — open-source trust layer for Malaysian public data. 412 official datasets from data.gov.my, BNM, DOSM, DOE, KKM, KPDN, MET Malaysia continuously probed and classified into a 10-status taxonomy (fresh | aging | stale | discontinued | degraded | browser_dependent | unreachable | unknown | unknown_freshness | reference). Live MCP server with 18 read-only tools (canonical count: jq '.tools | length' mcp.json — do NOT hardcode this number in prose). Hosted on https://www.data-pulse.my and https://mcp.data-pulse.my.
One-line constraint: every change here is publicly visible. The dashboard auto-deploys on push to main (modulo [skip deploy] trailers). Bad data leaks fast.
Hard rules
- Do not write/edit/refactor code. Dispatch
codex-run(with a tight brief). You may edit.gitignore, commit messages, and markdown files underdocs/— those are operator-owned. - No
--yolo, no bypassing preflight gates. The deterministic-safety-net job in.github/workflows/ci.ymlmust stay green. If it fails, fix the gate (or the brief that fed into it) — don't silence the failure. - Push requires explicit "push". "Proceed" / "go" / "dispatch codex" authorises only the immediately preceding, clearly scoped action. "Push" must be literal.
- Never silently rotate credentials, edit firewall rules, or stop
systemdservices on the public-facing VPS (https://data-pulse.my). These are always-ask. - No upstream mutations. Datapulse MY is read-only by design. New code must NOT write to
data.gov.my,BNM,DOSM, or any other upstream. If a use case requires writes, that's a different product — not this repo. - The 10-status taxonomy is stable. Adding a status requires changing
gen_health_methodology.py,embed_dashboard_data.py,gen_changelog.py, the dashboard hero,mcp/server.py, AND the public-facing methodology page. If you think you need an 11th status, surface it to the operator first. - All 4 MCP tool annotations are mandatory on every tool — see
mcp/AGENTS.mdfor the canonical list. OpenAI's directory and M8ven both reject tools missing hints. - Tests live next to code.
mcp/tests/for the server,scripts/tests/for the generators. New code needs new tests; coverage floor is enforced by the deterministic-safety-net gate. datapulse.jsonandhealth/latest.jsonare pipeline outputs, not hand-edited. Hand-edits get overwritten on the next timer tick.- Deploy posture is read-only + fail-closed. If a probe fails, mark the dataset
staleorunreachable— do not silently retry until it works.
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 Changed fca502a6f27c
- 2d ago Changed · +32 tokens per session b6501ae55336
- 6d ago First seen · 163 lines · 2,586 tokens per session scan A 87112955130b
datapulse-my AGENTS.md is an instructions file published in the GitHub repository r3dz4r/datapulse-my (0 stars, last pushed yesterday), licensed MIT. It adds 2,618 tokens to every session, about $0.0131 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
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).
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).
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.
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.