agentmods.dev

data-control-center AGENTS.md

data-control-center AGENTS.md is an instructions file for Codex, OpenCode from hypertrial/data-control-center. It costs 864 tokens per session, scanned A, original, MIT.

Repository instructions for Data Control Center, a local-only app for uploading, profiling, exploring, and querying datasets. The frontend and backend technologies, setup commands, and security boundaries are specified.

In plain words
What is it for?
Use them when developing or validating the app, changing its frontend or backend, handling local uploads, or updating dependencies and project commands.
Why use it?
They help keep user data on the workstation and prevent changes that would accidentally introduce hosting, shared access, accounts, or other unsupported assumptions.

Instructions file for CodexOpenCode

not rated 5 1mo ago A scan 864 tokens original MIT
View the source file hypertrial/data-control-center
Install

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.

agentmods
npx agentmods add instructions/hypertrial/data-control-center/agents-md
Clone the repo
git clone --depth 1 https://github.com/hypertrial/data-control-center

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for data-control-center AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hypertrial/data-control-center/agents-md.svg)](https://agentmods.dev/instructions/hypertrial/data-control-center/agents-md)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 864 This file is loaded in full into every session.
When invoked 864 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00864 $0.00864
Opus 5 $0.00432 $0.00432
Sonnet 5 $0.00173 $0.00173
Haiku 4.5 $0.00086 $0.00086

Measured 3d ago against content hash 2a822908e64b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

AGENTS.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Project Overview

Data Control Center is a local-only workstation app for uploading, profiling, exploring, and querying local datasets.

  • Frontend: frontend/ uses React, Vite, TypeScript, TanStack Query/Table, Zustand, ECharts, Tailwind, and shadcn-style primitives.
  • Backend: backend/ uses FastAPI, DuckDB, Polars, Pydantic, and uv.
  • Keep the product local-only. Do not introduce hosted, multi-user, shared-LAN, tenancy, or account-auth assumptions without an explicit user request.

Setup and validation

Run commands from the repository root unless noted. Canonical commands and CI parity: CONTRIBUTING.md (setup, Makefile targets, validation, coverage).

Quick reference:

  • make install / make dev — dependencies and local dev servers
  • make check — full validation before finishing work
  • make check-ci — after frontend lockfile changes
  • cd backend && uv sync --extra dev — after backend uv.lock / pyproject changes, then make check
  • make clean-local — discard local workspace and uploads

Use Node 22 from .nvmrc (matches CI). Use Python 3.11+ with uv.

If a required tool is missing or a network-dependent audit cannot run, state the exact blocker and any fallback checks performed.

Code Style

  • Follow existing module boundaries and naming before adding new abstractions.
  • Backend API routes live in backend/app/api/; Pydantic models in backend/app/models/; service logic in backend/app/services/.
  • Frontend API client/types live in frontend/src/api/; feature UI lives in frontend/src/features/; reusable primitives live in frontend/src/components/.
  • Add or update tests with behavior changes. Backend coverage is expected to remain at 100%; frontend coverage must satisfy the configured Vitest baseline.
  • Keep generated artifacts, coverage output, local databases, uploads, caches, and private datasets out of commits.
  • Prefer small, focused changes over broad refactors. Do not rewrite unrelated code while fixing a local issue.

Read the full file on GitHub · 84 lines

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.

  1. 3d ago First seen · 84 lines · 864 tokens per session scan A 2a822908e64b

Subscribe to this mod's changes

data-control-center AGENTS.md is an instructions file published in the GitHub repository hypertrial/data-control-center (5 stars, last pushed 1mo ago), licensed MIT. It adds 864 tokens to every session, about $0.0043 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.

Analytics and metricsData and AI
Related

Other instructions, from other repositories

GPT-RAG release.instructions.md

Instructions for Azure/GPT-RAG, a project described as: Sharing the learning along the way we been gathering to enable Azure OpenAI at enterprise scale in a secure manner. GPT-RAG core is a Retrieval-Augmented Generation pattern running in Azure, using Azure Cognitive Search for retrieval and Azure OpenAI large…

Azure/GPT-RAG · 207 tokens

plamen CLAUDE.md

Claude Code instructions for PlamenTSV/plamen, covering plamen — security auditor, execution model, reference files and shared.

PlamenTSV/plamen · 1,396 tokens

ZipAI CLAUDE.md

Claude Code instructions for nickdesi/ZipAI, covering claude.md — zipai: ultra-dense token optimizer, rules, 1. zero filler, 2. ambiguity and 3. prompt caching.

nickdesi/ZipAI · 1,204 tokens

TreeSkill CLAUDE.md

Instructions for JimmyMa99/TreeSkill, covering claude.md, project overview, commands, install and run tests.

JimmyMa99/TreeSkill · 1,248 tokens

tshark-mcp copilot-instructions.md

Copilot instructions for ouonet/tshark-mcp: Project: MCP server for using TShark to analyze network packets. Language: Python.

ouonet/tshark-mcp · 128 tokens

Copilot-Skills langchain.instructions.md

Instructions for TheSethRose/Copilot-Skills, covering langchain instructions, default behaviors, common workflows, basic chain setup and with claude.

TheSethRose/Copilot-Skills · 1,269 tokens