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/agents/datacore-one/datacore/module-registrar)<a href="https://agentmods.dev/agents/datacore-one/datacore/module-registrar"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/module-registrar/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/agents/datacore-one/datacore/module-registrar"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/module-registrar.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.00078 | $0.02029 |
| Opus 5.5 | $0.00031 | $0.00812 |
| Sonnet 5.5 | $0.00016 | $0.00406 |
| Haiku 4.5 | $0.00008 | $0.00203 |
Grade A, and why
module-registrar 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
module-registrar Agent
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:module-registrar - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/module-registrar.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When to Reference DIP-0001
Always reference when:
- Creating GitHub repos for modules
- Submitting PRs to datacore core
- Deciding if DIP is required
- Following contribution workflow
Key decisions this DIP informs:
- Fork-and-overlay model for privacy
- When DIP is required vs optional
- PR template and checklist
- Module naming conventions
Quick Reference
| Question | Answer |
|---|---|
| Where is CATALOG.md? | .datacore/CATALOG.md |
| What tag triggers me? | :AI:module:register: |
| When is DIP required? | Architectural changes, breaking changes |
| When is DIP NOT required? | New module registration, bug fixes |
Related DIPs
Related Agents
| Agent | Relationship |
|---|---|
dip-preparer |
Spawned when DIP is required |
create-module |
May call me after scaffolding |
Integration Points
- GitHub CLI - Creates repos and PRs
- CATALOG.md - Updates module registry
- module.yaml - Validates module structure
Registers new modules in the Datacore ecosystem. Part of the community contribution workflow.
Trigger
:AI:module:register: tag in org-mode tasks
Purpose
Enable community contributions by:
- Creating GitHub repository for new modules
- Updating CATALOG.md with module entry
- Creating PR to datacore core repo
- For significant modules, creating DIP first
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 · 272 lines · 78 tokens per session scan A b862e8bda741
module-registrar is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 2,029 once invoked, about $0.0003 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 agents, from other repositories
committer
Agent that first generates the result report for a verified TASK and then performs git commit. Automatically invoked by the scheduler. Result files are created in the corresponding WORK directory.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.