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 instructions/macrocosm-os/dataverse-cli/agents-mdgit clone --depth 1 https://github.com/macrocosm-os/dataverse-cliWhat 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.01286 | $0.01286 |
| Opus 5 | $0.00643 | $0.00643 |
| Sonnet 5 | $0.00257 | $0.00257 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
dataverse-cli 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 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dataverse CLI — Agent Integration Guide
Binary: dv
Dataverse CLI provides real-time social media data from X/Twitter and Reddit via the Bittensor SN13 decentralized data network (Macrocosmos).
Machine-Readable Command Catalog
dv commands
Emits a full JSON schema of all commands, flags, types, defaults, enums, examples, and API endpoint mappings. Use this to discover capabilities programmatically.
Quick Start for Agents
# Set API key (get free at https://app.macrocosmos.ai/account?tab=api-keys)
export MC_API="your-key"
# Always use -o json for structured output
dv -o json search x -k bittensor -l 10
# Preview request without executing (no API call, no credits consumed)
dv --dry-run search x -k bitcoin -l 5
Output Modes
| Flag | Format | Use Case |
|---|---|---|
-o table |
Human-readable table (default) | Interactive terminal |
-o json |
JSON array to stdout | Agent parsing, piping to jq |
-o csv |
CSV to stdout | Data analysis, spreadsheets |
Convention: Data goes to stdout, diagnostics/errors go to stderr. Safe to pipe stdout.
Response Structure (JSON mode)
Search (dv -o json search ...)
Returns a JSON array of post objects. Each post has:
{
"datetime": "2026-03-17T14:53:00Z",
"source": "x",
"text": "Post content...",
"uri": "https://x.com/user/status/123",
"user": {
"username": "handle",
"display_name": "Display Name",
"followers_count": 1234,
"user_blue_verified": true
},
"tweet": {
"id": "123456",
"like_count": 42,
"retweet_count": 5,
"reply_count": 3,
"view_count": 1000,
"hashtags": ["#bittensor"],
"language": "en"
}
}
Dry Run (dv --dry-run ...)
Returns the exact HTTP request that would be sent:
{
"method": "POST",
"url": "https://constellation.api.cloud.macrocosmos.ai/sn13.v1.Sn13Service/OnDemandData",
"headers": { "authorization": "Bearer 87ae...c800", "content-type": "application/json" },
"body": { "source": "X", "keywords": ["bittensor"], "limit": 10 }
}
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 · 146 lines · 1,286 tokens per session scan A 904a263ccc4a
dataverse-cli AGENTS.md is an instructions file published in the GitHub repository macrocosm-os/dataverse-cli (118 stars, last pushed 12d ago), licensed MIT. It adds 1,286 tokens to every session, about $0.0064 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-30.
Other instructions, from other repositories
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).
next.js 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, applying the notice (cutover) and fallback chain (never fail the build).
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.
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.