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/structural-integrity)<a href="https://agentmods.dev/commands/datacore-one/datacore/structural-integrity"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/structural-integrity/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/structural-integrity"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/structural-integrity.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.00019 | $0.00775 |
| Opus 5.5 | $0.00008 | $0.00310 |
| Sonnet 5.5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
structural-integrity 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/structural-integrity Command
Command Context
When to Reference DIP-0015
Always reference when:
- Validating folder hierarchy
- Checking companion file requirements
- Detecting naming violations
- Checking that no binaries are committed to git (Datacore does not use Git LFS)
Key decisions this DIP informs:
- Expected folder structure (0-inbox/, 1-tracks/, etc.)
- Companion requirements for non-readable files
- Binaries stay gitignored (no Git LFS)
- Naming convention (kebab-case)
Quick Reference
| Question | Answer |
|---|---|
| Expected structure? | 0-inbox/, 1-tracks/, 3-knowledge/, 4-archive/ |
| Companion required? | .key, .pptx, .psd, .ai files |
| Binaries in git? | Never — gitignored, companion committed |
| What DIPs govern this? | DIP-0015 (Semantic Org), DIP-0002 (Layers) |
Agents This Command Invokes
| Agent | Purpose |
|---|---|
structural-integrity |
Audit and fix |
Integration Points
- DIP-0015 - Folder structure specification
- /ingest - Triggers post-ingest check
- /gtd-weekly-review - Weekly audit
Audit and maintain the organizational structure of Datacore.
Usage
/structural-integrity [check|report|fix]
check- Quick scan, return pass/fail with summary (default)report- Detailed diagnostic of all issues foundfix- Attempt automatic corrections (with confirmation)
What It Detects
| Issue Type | Severity |
|---|---|
| Misplaced files | ⚠️ Warning |
| Missing companions (.key without .md) | ⚠️ Warning |
| Orphaned companions | ❌ Error |
| Missing _index.md | ℹ️ Info |
| Naming violations | ℹ️ Info |
| Unprocessed inbox (>7 days) | ⚠️ Warning |
| Binary tracked by git | ❌ Error |
| Broken wiki-links | ⚠️ Warning |
Examples
/structural-integrity # Quick check
/structural-integrity check # Same as above
/structural-integrity report # Detailed report
/structural-integrity fix # Attempt fixes
/sif # Alias for check
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.
- 2d ago Changed c85e7da5c71b
- 1mo ago First seen · 118 lines · 19 tokens per session scan A 45162ed45d75
structural-integrity is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 775 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
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
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…
create-issue
Create a GitHub issue with proper template discovery and population.
prepare-release
Prepare a version release — follows project release config in .aicontext/release.md, runs first-time setup if config is missing.
run-task
Run pending steps, then aftertask finalization; does not close the task.
finish-task
Deprecated alias for close-task.