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.
git clone --depth 1 https://github.com/datacore-one/datacoreWrote 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/datacore-one/datacore/create-module)<a href="https://agentmods.dev/commands/datacore-one/datacore/create-module"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/create-module/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/commands/datacore-one/datacore/create-module"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/create-module.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.00006 | $0.01065 |
| Opus 5.5 | $0.00002 | $0.00426 |
| Sonnet 5.5 | $0.00001 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
create-module 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-module
Command Context
When to Reference DIP-0007
Always reference when:
- Creating module structure
- Validating module.yaml
- Checking required files
- Auditing existing modules
Key decisions this DIP informs:
- Required files (module.yaml, CLAUDE.base.md)
- Settings section format
- Provides section structure
- Hook definitions
Quick Reference
| Question | Answer |
|---|---|
| Required files? | module.yaml, CLAUDE.base.md, .gitignore |
| Module location? | .datacore/modules/<name>/ |
| Command style? | Conversational, not CLI wrapper |
| What DIPs govern this? | DIP-0007 (Module Spec), DIP-0002 (Layers) |
Agents This Command Invokes
| Agent | Purpose |
|---|---|
create-module |
Scaffold/convert/audit |
module-registrar |
CATALOG registration |
Integration Points
- DIP-0007 - Module specification
- DIP-0002 - Layered context pattern
- Trading module - Reference implementation
Create, convert, or audit Datacore modules for spec alignment.
Workflow
Step 1: Understand Intent
If user invoked /create-module with no clear intent, ask:
"What would you like to do?"
- Create new - Start a new module from scratch with correct structure
- Convert existing - Turn existing code into a spec-aligned module
- Audit - Check an existing module for spec alignment and suggest improvements
If intent is clear from context (e.g., "make datacortex a module"), proceed directly.
Step 2: Gather Information
For new module:
- Ask: "What should the module be called?" (lowercase, hyphenated)
- Ask: "What does it do?" (one-line description)
- Ask: "What will it provide?" (commands, agents, templates)
- Default location:
.datacore/modules/<name>
For conversion:
- Ask: "Where is the code?" (path to existing project)
- Then same questions as new module
For audit:
- Ask: "Which module?" (path or name)
Step 3: Execute
Invoke the create-module agent with gathered information.
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 First seen · 180 lines · 6 tokens per session scan A 4dd04cd68f58
create-module is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 1,065 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
voice-refresh
Refresh the founder-voice DNA from new Granola meetings (interactive, MCP-backed). Pulls meetings since the last refresh, harvests Assaf-only speech, runs the Stage 2-3 orchestrator, and presents a founder-gated delta. Never auto-writes voice-dna.md.
decompose
Feature/story breakdown — consume a ready-for-decompose scope doc and produce a task graph in the issue tracker. Re-entrant; tracker-as-canonical with vault breadcrumb.
memory-sprint
Show current sprint state from StudioMeyer Memory.
draft-issue
Draft a GitHub issue based on a discussion or requirements in the current conversation.
close-task
Close the task: update tracking and optionally its GitHub issue.