Borrowing it
Nothing to install: this file belongs to hypertrial/data-control-center. 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/hypertrial/data-control-center/main/AGENTS.mdgit clone --depth 1 https://github.com/hypertrial/data-control-centerWrote 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/hypertrial/data-control-center/agents-md)<a href="https://agentmods.dev/instructions/hypertrial/data-control-center/agents-md"><img src="https://agentmods.dev/badge/instructions/hypertrial/data-control-center/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/hypertrial/data-control-center/agents-md"><img src="https://agentmods.dev/badge/instructions/hypertrial/data-control-center/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.00406 | $0.00406 |
| Opus 5.5 | $0.00162 | $0.00162 |
| Sonnet 5.5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
data-control-center 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 1mo 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.
What it actually says
Agent entry point
This repository uses the Universal Pad specification for non-trivial agentic work.
Git is the source of truth for code. CI is the source of truth for verification. Pad is the source of truth for intent, scope, status, dependencies, decisions, evidence, and handoffs.
Read PROJECT_AGENT.md before implementation. It holds repository-specific invariants, stack notes, and the native verification commands wrapped by scripts/verify-fast and scripts/verify.
Work
Use Pad collections Work and Plans only.
Work types: Feature, Bug, Refactor, Investigation, Maintenance. Plans are multi-ticket containers only.
Statuses (machine values): backlog, ready, in-progress, blocked, review, done.
Risk: r0 (trivial), r1 (normal), r2 (consequential), r3 (critical).
Do not create Ideas, Tasks, chores, or extra default types. Do not run the Pad onboard playbook.
Lifecycle
specify → test/reproduce → implement → targeted verification → full verification → adversarial review → fix findings → re-verify → CI → evidence → done
Do not start material implementation until the ticket is ready: intended behavior, invariants, regression surface, and verification are specified.
Implement the smallest coherent change. Do not silently expand scope. Put unrelated work in a new Pad ticket.
Verification
Development feedback: scripts/verify-fast
Completion gate: scripts/verify
A ticket is not done while required verification is failing or unrun. Record why if a required command cannot run.
Evidence and handoffs
Record decisions with pad item decide. Represent blockers as Pad dependencies, not prose.
Incomplete work must include a handoff a fresh agent can resume without chat history.
R2/R3 work needs independent adversarial review before done.
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.
- 1mo ago Changed · -40 lines · -458 tokens per session 8e0e7df28f0d
- 2mo ago First seen · 84 lines · 864 tokens per session scan A 2a822908e64b
data-control-center AGENTS.md is an instructions file published in the GitHub repository hypertrial/data-control-center (4 stars, last pushed 1mo ago), licensed MIT. It adds 406 tokens to every session, about $0.0016 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.