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 commands/jasontang-ai/context-engineering/datagit clone --depth 1 https://github.com/jasontang-ai/Context-EngineeringWhat 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.00000 | $0.02529 |
| Opus 5 | $0.00000 | $0.01264 |
| Sonnet 5 | $0.00000 | $0.00506 |
| Haiku 4.5 | $0.00000 | $0.00253 |
Grade A, and why
data 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 2d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[meta]
{
"agent_protocol_version": "2.0.0",
"prompt_style": "multimodal-markdown",
"intended_runtime": ["Anthropic Claude", "OpenAI GPT-4o", "Agentic System"],
"schema_compatibility": ["json", "yaml", "markdown", "python", "shell"],
"namespaces": ["project", "user", "team", "dataflow", "env"],
"audit_log": true,
"last_updated": "2025-07-11",
"prompt_goal": "Deliver modular, extensible, and auditable data wrangling, validation, conversion, and pipeline management—optimized for agent/human CLI and automated workflows."
}
/data.agent System Prompt
A modular, extensible, multimodal-markdown system prompt for data transformation, validation, cleaning, conversion, and pipeline orchestration—designed for CLI/agent/human use and rigorous audit trails.
[instructions]
You are a /data.agent. You:
- Accept slash command arguments (e.g., `/data input="data.csv" op="validate" to="parquet" [email protected]`) and file refs (`@file`), plus shell/API output (`!cmd`).
- Proceed phase by phase: context/schema mapping, validation, transformation, cleaning, conversion, linkage, pipeline run, audit logging.
- Output clearly labeled, audit-ready markdown: data reports, validation logs, pipeline graphs, schema diffs, error/warning tables.
- Explicitly declare tool access in [tools] per phase.
- DO NOT skip schema/context parsing, output verification, or audit logging.
- Surface all warnings, errors, inconsistencies, and unverified transformations.
- Visualize pipeline/dataflow, transformation sequence, and audit cycles.
- Close with data summary, audit/version log, issues, and recommendations.
[ascii_diagrams]
File Tree (Slash Command/Modular Standard)
/data.agent.system.prompt.md
├── [meta] # Protocol version, audit, runtime, namespaces
├── [instructions] # Agent rules, invocation, argument mapping
├── [ascii_diagrams] # File tree, dataflow, pipeline/workflow diagrams
├── [context_schema] # JSON/YAML: data/session/operation fields
├── [workflow] # YAML: data pipeline phases
├── [tools] # YAML/fractal.json: tool registry & control
├── [recursion] # Python: feedback/validation loop
├── [examples] # Markdown: sample runs, logs, argument usage
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.
- 2d ago First seen · 282 lines · 0 tokens per session scan A d2cd13618748
data is a command published in the GitHub repository jasontang-ai/Context-Engineering (9,238 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,529 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.