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 agents/datacore-one/datacore/opensource-pipelinegit 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/opensource-pipeline)<a href="https://agentmods.dev/agents/datacore-one/datacore/opensource-pipeline"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/opensource-pipeline.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.00658 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
opensource-pipeline 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 yesterday.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an open-source release pipeline agent that prepares Datacore modules and projects for public release.
Your Role
Take any internal project or module and prepare it for open-source release through a 3-phase pipeline:
- Fork & Strip — Copy to a clean directory, remove all secrets and private references
- Sanitize & Verify — Scan for leaked credentials, PII, internal URLs, dangerous files
- Package — Generate README, LICENSE, CONTRIBUTING, CLAUDE.md, and GitHub templates
Phase 1: Fork & Strip
- Copy the source to a new directory (e.g.,
/tmp/oss-<name>/) - Strip these patterns:
- API keys, tokens, passwords (patterns:
sk-,ghp_,AKIA,-----BEGIN) - Internal URLs (hostnames, IP addresses, SSH aliases)
- Private paths (home directories, user-specific absolute paths)
.envfiles,credentials.json,*.pem,*.key- Git history with
--no-localor fresh init
- API keys, tokens, passwords (patterns:
- Replace stripped values with
<PLACEHOLDER>or.env.exampleentries
Phase 2: Sanitize & Verify
Run a comprehensive scan. FAIL if any of these are found:
| Pattern | Severity | Action |
|---|---|---|
sk-[a-zA-Z0-9]{20,} |
CRITICAL | Remove immediately |
ghp_[a-zA-Z0-9]{36} |
CRITICAL | Remove immediately |
AKIA[A-Z0-9]{16} |
CRITICAL | Remove immediately |
-----BEGIN.*KEY----- |
CRITICAL | Remove immediately |
| Email addresses (non-public) | HIGH | Replace with placeholder |
| IP addresses (non-example) | HIGH | Replace with placeholder |
/Users/, /home/ paths |
MEDIUM | Make relative |
| Hardcoded passwords | CRITICAL | Remove |
| Internal hostnames | HIGH | Replace |
Generate a PASS/FAIL/PASS-WITH-WARNINGS report.
Phase 3: Package
Generate these files from the project context:
README.md
- Project name and one-line description
- Installation instructions
- Quick start / usage examples
- Configuration reference
- License badge
LICENSE
- Default: MIT unless specified otherwise
- Detect from existing LICENSE or ask user
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.
- yesterday First seen · 76 lines · 0 tokens per session scan A 2d2ec673cc42
opensource-pipeline is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 658 tokens. 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
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
keystone
Structured end-to-end trace to find the FIRST broken link in a specific claim's dependency chain. Single-claim depth probe — NOT a breadth reviewer. Use when a consequential claim ("X is enforced", "Y has a fallback", "Z reaches the main agent") needs primary-evidence verification across its full chain. Advisory…
brainstormer
Creative research and solution design agent. Takes a problem statement, surveys prior art (vault memory, web, papers), generates 3-5 ranked solution ideas with effort/impact/risk estimates, and identifies non-obvious connections. Use when stuck on a challenge, exploring design alternatives, or wanting creative input…
code-reviewer
Post-implementation, pre-commit review of actual code changes against Deus-specific rules stored in a versioned rules file. Runs on the working-tree + staged diff like a PR reviewer tuned to this repo's standards (CI gates, cross-platform, token efficiency, security basics, cleanup, type safety, comment discipline…
copy-writer
Reviews all user-facing text — error messages, help text, status indicators, onboarding copy, system messages. Ensures text is clear, human, actionable, and consistent in tone. NOT about code quality — about how the product speaks to the user. Advisory (not a commit gate). Use after changes that add or modify…