obsidian-university-workflow: Command for Claude Code

.claude/commands/improve-templates.md

improve-templates is a command for Claude Code from ABO896/obsidian-university-workflow. It costs 48 tokens per session (1,055 once invoked), scanned A, original, MIT.

A command for auditing and improving every template in an Obsidian Templater project, a note-taking project that uses reusable templates.

In plain words
What is it for?
It examines project files, templates, scripts, documentation, and conventions, then proposes improvements and new features.
Why use it?
It structures a full project review so templates and scripts are understood before changes are written, using the official Templater API documentation.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is ABO896/obsidian-university-workflow's own configuration. It tells Claude Code how to work on obsidian-university-workflow itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything obsidian-university-workflow configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ABO896/obsidian-university-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ABO896/obsidian-university-workflow/main/.claude/commands/improve-templates.md
Clone the repo
git clone --depth 1 https://github.com/ABO896/obsidian-university-workflow

Made for: Claude Code.

Wrote 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.

agentmods badge for improve-templates

README.md
[![agentmods](https://agentmods.dev/badge/commands/abo896/obsidian-university-workflow/improve-templates/github.svg)](https://agentmods.dev/commands/abo896/obsidian-university-workflow/improve-templates)
Your own site
<a href="https://agentmods.dev/commands/abo896/obsidian-university-workflow/improve-templates"><img src="https://agentmods.dev/badge/commands/abo896/obsidian-university-workflow/improve-templates/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.

agentmods 80×15 button for improve-templates

Your own site · 80×15
<a href="https://agentmods.dev/commands/abo896/obsidian-university-workflow/improve-templates"><img src="https://agentmods.dev/badge/commands/abo896/obsidian-university-workflow/improve-templates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,055 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.01055
Opus 5 $0.00024 $0.00528
Sonnet 5 $0.00010 $0.00211
Haiku 4.5 $0.00005 $0.00105

Measured 10d ago against content hash f6cf33001676, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

improve-templates 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.

.claude/commands/improve-templates.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are about to do a deep audit and improvement pass on this Obsidian Templater project. Follow every phase in order. Do not skip phases. Do not write any template code until Phase 2.


Phase 1 — Understand the Project

Read and analyse the entire project thoroughly:

  1. Read CLAUDE.md if it exists
  2. Use Glob to find every file in the vault (**/*.md, **/*.js, **/*.ts)
  3. Read every template file (look in folders named Templates, templates, _templates or similar)
  4. Read every user script (.js files in the scripts folder configured in Templater settings)
  5. Read the README or any docs files
  6. Identify:
    • The purpose and goal of this vault/project
    • The folder structure and how it's organised
    • Every template and what it does
    • Every Templater user script and what it does
    • Any patterns, workflows, or conventions used across templates
    • Anything that looks broken, inconsistent, or overly complex

Summarise your findings before moving to Phase 2.


Phase 2 — Read the Full Templater Documentation

Read .claude/skills/templater-docs/templater-api.md in full using the Read tool.

Do not skip sections. Pay attention to:

  • Every module: tp.date, tp.file, tp.frontmatter, tp.system, tp.web, tp.app, tp.config, tp.hooks, tp.obsidian, tp.user
  • All function signatures and optional arguments
  • All command types: <% %>, <%* %>, <%+ %> and whitespace control -%> <%-
  • User script patterns (CommonJS exports, passing tp as argument)
  • The tR output variable and how to use it
  • The tp.hooks.on_all_templates_executed pattern
  • Dynamic commands and their known limitations

Do not proceed to Phase 3 until you have read the full PDF.


Phase 3 — Audit All Templates

Go through every template one by one. For each template, check:

Raw JS that should be Templater API:

  • Any new Date() → should be tp.date.now()
  • Any window.prompt() or prompt() → should be await tp.system.prompt()
  • Any fetch() or manual HTTP → should be await tp.web.request()
  • Any manual frontmatter parsing → should be tp.frontmatter.key
  • Any app.* calls → should use tp.app.*
  • Any moment() calls that could be tp.date.*

Read the full file on GitHub · 110 lines

Changes

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.

  1. 10d ago First seen · 110 lines · 48 tokens per session scan A f6cf33001676

Subscribe to this mod's changes

improve-templates is a command published in the GitHub repository ABO896/obsidian-university-workflow (23 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,055 once invoked, about $0.0002 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-30.