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/chrismo/superdb-mcp/syncgit clone --depth 1 https://github.com/chrismo/superdb-mcpWrote 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/commands/chrismo/superdb-mcp/sync)<a href="https://agentmods.dev/commands/chrismo/superdb-mcp/sync"><img src="https://agentmods.dev/badge/commands/chrismo/superdb-mcp/sync.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 | $0.00000 | $0.01129 |
| Opus 5 | $0.00000 | $0.00564 |
| Sonnet 5 | $0.00000 | $0.00226 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
sync scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Fetch `https://raw.githubusercontent.com/chrismo/asdf-superdb/main/scripts/versions.txt` using curl How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync SuperDB Docs
Check for upstream SuperDB breaking changes and verify LSP version sync.
This command runs autonomously. No user confirmation required.
Context
All docs, tutorials, recipes, and grok patterns are consumed from the @chrismo/superkit npm package — superkit is the single source of truth. The upstream SuperDB repo (brimdata/super) may introduce breaking changes that need to be reflected in superkit's migration guide and expert doc; this command surfaces those so they can be addressed upstream in superkit and then pulled in here via a dependency bump.
Execution Plan
Phase 1: Breaking Change Scan
This phase is informational only — it reports findings for human review, doesn't auto-update anything.
Step 1: Extract current doc version
Read the frontmatter from node_modules/@chrismo/superkit/docs/zq-to-super-upgrades.md to get the current superdb_version. (Docs come from the superkit npm package — there is no local docs/ directory.)
Step 2: Check asdf-superdb versions.txt
- Fetch
https://raw.githubusercontent.com/chrismo/asdf-superdb/main/scripts/versions.txtusing curl - Parse versions.txt to find all comment blocks containing "breaking" (case-insensitive) that appear after the current doc version's entries
- Report any found with their associated PR links
Step 3: Check LSP CHANGELOG
- Fetch
https://raw.githubusercontent.com/chrismo/superdb-lsp/main/CHANGELOG.mdusing curl - Extract entries newer than the current doc version
- Surface any "Changed", "Breaking", or "Removed" sections
- If CHANGELOG is unavailable or empty, note that and move on
Step 4: Investigate breaking changes with research.sh
If breaking changes were found in Steps 2-3, use ./scripts/research.sh to gather context:
# Search issues/PRs for details on a breaking change
./scripts/research.sh search "string concatenation"
# Find the relevant commits
./scripts/research.sh commits "concat operator"
# Read the full issue/PR discussion
./scripts/research.sh issue 6486
# Check if docs were updated for the change
./scripts/research.sh code "concat"
# Compare doc pages across releases
./scripts/research.sh docs super-sql/expressions/intro --ref v0.1.0
./scripts/research.sh docs super-sql/expressions/intro --ref main
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.
- 3d ago First seen · 112 lines · 0 tokens per session scan A 0654158a6497
sync is a command published in the GitHub repository chrismo/superdb-mcp (0 stars, last pushed 1mo ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,129 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.