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/spencermarx/obsidian-aiWrote 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/spencermarx/obsidian-ai/history)<a href="https://agentmods.dev/commands/spencermarx/obsidian-ai/history"><img src="https://agentmods.dev/badge/commands/spencermarx/obsidian-ai/history/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/spencermarx/obsidian-ai/history"><img src="https://agentmods.dev/badge/commands/spencermarx/obsidian-ai/history.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.00040 |
| Opus 5 | $0.00003 | $0.00020 |
| Sonnet 5 | $0.00001 | $0.00008 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
history 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 10d 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.
This is a copy
100% identical to history — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
OCR: History
This command is managed by Open Code Review.
Execute this command by reading and following: .ocr/commands/history.md
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.
- 10d ago First seen · 10 lines · 6 tokens per session scan A 01fc2f7f8745
history is a command published in the GitHub repository spencermarx/obsidian-ai (48 stars, last pushed 4mo ago), licensed MIT. It adds 6 tokens to every session and 40 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to history, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
scaffold-fullstack
Initialize a new fullstack Go + React project with standard directory structure, configs, and Docker Compose.
el-capitan
Orchestrate the full fullstack development pipeline. Read the workflow YAML, dispatch workers via Task tool, validate gates, report results.
scaffold-mean
One-time project setup for a MEAN stack application. Initializes the project structure, installs dependencies, and creates base configuration files. Run this ONCE before the first /el-capitan invocation.
jira-create
Create a new Jira ticket using the Atlassian MCP server.
jira-comment
Add a comment to a Jira ticket using the Atlassian MCP server.
jira-link
Link two Jira tickets using the Atlassian MCP server.