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.
curl -O https://raw.githubusercontent.com/ABO896/obsidian-university-workflow/main/AGENTS.mdgit clone --depth 1 https://github.com/ABO896/obsidian-university-workflowWrote 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/instructions/abo896/obsidian-university-workflow/agents-md)<a href="https://agentmods.dev/instructions/abo896/obsidian-university-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/abo896/obsidian-university-workflow/agents-md.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.1 | $0.00536 | $0.00536 |
| Opus 5 | $0.00268 | $0.00268 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
obsidian-university-workflow AGENTS.md 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 7d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Project Guidance (Obsidian University Workflow)
You are working inside my Obsidian vault. Be helpful, focused, and careful.
Scope & Layout
- Repo root is the vault root. Respect
.gitignore. - Personal notes outside the areas below are out of scope unless I ask.
What You May Edit (balanced)
_templates/**— create/modify/refactor templates._templater_scripts/**— create/modify/refactor Templater user scripts.- Files directly referenced by those (e.g., shared helper MD/JSON under the same folders).
README.md,AGENTS.md— update docs to explain new templates/scripts.
You may create new files/folders inside
_templates/and_templater_scripts/as needed (e.g.,_templates/daily/…,_templater_scripts/utils/…).
Knowledge Base
- If present, prefer
.codex_kb/*.mdfor canonical rules (naming, frontmatter, date formats, workflows). - Don’t read or reference personal notes outside
.codex_kbunless I ask.
Templater & Scripts
- Use Templater APIs (
tp.file,tp.date,tp.frontmatter,tp.user.*). - Keep scripts deterministic and local (no network, no secrets).
- File names:
kebab-case.js; functions:camelCase. - Add a short top comment for non-obvious scripts (purpose, inputs, outputs).
Templates
- Put new templates under
_templates/…with clear names. - Include minimal frontmatter; never hard-code secrets.
- When a template depends on a script, add a top comment with its path.
Quality & Safety
- Prefer small, targeted diffs; don’t churn unrelated files.
- If making broad changes, show a brief plan and example output.
- Validate basic Templater rendering (no runtime errors) before proposing.
Allowed Improvements
- Refactor scripts into shared utilities.
- Extract duplicated template snippets.
- Rename/move within the allowed folders to improve organization (update references).
Hard No’s
- Do not touch personal notes/journals or move files outside the allowed folders without my say-so.
- Do not change
.gitignore, delete user content, or add networked code. - Do not leak or assume secrets.
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.
- 7d ago First seen · 59 lines · 536 tokens per session scan A 7335e2717c3b
obsidian-university-workflow AGENTS.md is an instructions file published in the GitHub repository ABO896/obsidian-university-workflow (23 stars, last pushed 1mo ago), licensed MIT. It adds 536 tokens to every session, about $0.0027 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.