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/opensource)<a href="https://agentmods.dev/commands/datacore-one/datacore/opensource"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/opensource/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/opensource"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/opensource.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.00026 | $0.00406 |
| Opus 5.5 | $0.00010 | $0.00162 |
| Sonnet 5.5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
opensource 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.
What it actually says
/opensource Command
Prepare any Datacore module, project, or codebase for public open-source release.
Usage
/opensource <path> # Release a specific project
/opensource .datacore/modules/X # Release a module
/opensource --check <path> # Dry-run sanitization check only
Workflow
Phase 1: Assessment
- Read the target project/module
- Identify: license, existing README, dependencies, secrets risk areas
- Present release plan to user for approval
Phase 2: Execute Pipeline
Spawn the opensource-pipeline agent with the approved plan:
- Fork & Strip — Copy to clean directory, remove secrets/private paths
- Sanitize & Verify — Scan for leaked credentials, PII, internal URLs
- Package — Generate README, LICENSE, CONTRIBUTING, CLAUDE.md, GitHub templates
Phase 3: Publish
- Create GitHub repo (if doesn't exist) via
gh repo create - Push sanitized code
- Create initial release tag
- Update competitive landscape doc if relevant
Key Rules
- NEVER skip the sanitization scan
- Present the scan report to user before publishing
- Default license: MIT (unless project specifies otherwise)
- Preserve existing docs — enhance, don't replace
- For Datacore modules, follow DIP-0001 contribution model
Agent
Orchestrator: main conversation
Worker: opensource-pipeline agent (spawned for phases 2-3)
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 · 54 lines · 26 tokens per session scan A 423139e96670
opensource is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 406 once invoked, about $0.0001 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
changelog
Create engaging changelogs for recent merges to main branch.
update-infos-release
Update Claude Code releases tracking (guide + landing + version bump).
iteration-loop
Autonomous full iteration loop for cloud agents — Phase 1 (code-first direction lock, retained design prototype, compass/plans and selected Review & Edit) through Phase 2–6 (execute → close → PR → merge-ready → post-merge close). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 6 post-merge…
changelog
View recent CHANGELOG entries.
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable, then Phase 6 post-merge close once the PR is verified merged. Not Done until…
finish-branch-execute
Step 4 of finishing-a-development-branch: Execute chosen integration option (merge, PR, PR+dance, keep, or discard).