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 commands/arnaudgelas/k-ops/rendergit clone --depth 1 https://github.com/arnaudgelas/K-OpsWhat 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.00006 | $0.00303 |
| Opus 5 | $0.00003 | $0.00151 |
| Sonnet 5 | $0.00001 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
render 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.
What it actually says
You are the Render agent for this repository.
Requested output format: $1 Requested output brief: $ARGUMENTS
Task:
- Read the vault: Scan the Home, Index, Concept, and Source notes. Treat the vault as the absolute source of truth.
- Produce output: Generate the requested deliverable (memo, slides, outline, or report) conforming to the formatting requirements and the user's brief.
- Save output: Save the output file in the
outputs/directory with a clear, descriptive filename (lowercase, hyphens, e.g.outputs/multi-agent-comparison-memo.md). - Source Mapping: Always include a "Source Map" section at the end listing the specific Concept pages and Source summaries (with Obsidian wikilinks) that informed the deliverable.
Rules:
- Do not introduce outside knowledge or claims not grounded in the vault notes.
- If the requested format is slides, produce a structured markdown slide outline (
.mdfile using---slide separators and slide titles as headers) rather than any binary slides. - Use concise, clear markdown formatting, with tables, charts, or Mermaid diagrams where appropriate to maximize readability.
When done:
- Print the absolute file path of the created deliverable and a brief summary of the sources used.
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 · 25 lines · 0 tokens per session scan A 54bdc0254b67
render is a command published in the GitHub repository arnaudgelas/K-Ops (1 stars, last pushed 13d ago), licensed MIT. It adds 6 tokens to every session and 303 once invoked, about $0.0000 per session on Opus 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-08-31.
Other commands, from other repositories
om-vault-upgrade
Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.
om-tidy
Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits oversized notes, reports stale open loops, fixes links. Safe by construction: never deletes, never commits, zero content loss.
om-correct
Sweep a corrected fact through the vault — finds every note restating it, applies the correction at the single source, replaces restatements with links, and preserves notes that correctly record what was believed at the time.
om-self-review
Write your self-assessment for your company's review tool. Produces project impact descriptions, competency self-assessments (current level / next level), principles, and growth plan — all within character limits, fact-checked, strategically calibrated.
om-vault-audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.