Borrowing it
Nothing to install: this file belongs to benoror/obsidianos_work. 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/benoror/obsidianos_work/main/AGENTS.mdgit clone --depth 1 https://github.com/benoror/obsidianos_workWrote 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/benoror/obsidianos_work/agents-md)<a href="https://agentmods.dev/instructions/benoror/obsidianos_work/agents-md"><img src="https://agentmods.dev/badge/instructions/benoror/obsidianos_work/agents-md/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/instructions/benoror/obsidianos_work/agents-md"><img src="https://agentmods.dev/badge/instructions/benoror/obsidianos_work/agents-md.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.02627 | $0.02627 |
| Opus 5.5 | $0.01051 | $0.01051 |
| Sonnet 5.5 | $0.00525 | $0.00525 |
| Haiku 4.5 | $0.00263 | $0.00263 |
Grade A, and why
obsidianos_work 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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
This is an Obsidian vault with AI agent skills. See USER.md for the vault owner's identity. Agents working in this repo should be aware of the following structure and conventions.
Skills
Custom skills live in .agents/skills/. Each has a SKILL.md with usage, workflow, and conventions.
| Skill | What it does | Arguments |
|---|---|---|
| meeting | Create a meeting note | |
├ /meeting |
Pick from today's Google Calendar events | |
├ /meeting {title} |
Manual creation with today's date | folder={subfolder} |
├ /meeting wrap <path> |
Wrap up: mail-transcripts → cache → participants → todos → commit | |
└ /meeting wrap pending [dates] |
Find & wrap all pending meetings | today, yesterday, last week, 2026-01-01..2026-02-03 |
| cache-notes | Fetch & embed AI transcripts as Obsidian callouts | |
├ /cache-notes <path> |
Cache a specific meeting file (prompts for URLs if empty) | |
├ /cache-notes all |
Batch-cache all uncached meetings | |
└ /cache-notes refresh <path> |
Re-fetch and overwrite existing cache | |
| fill-participants | Resolve and fill Participants: frontmatter |
|
├ /fill-participants <path> |
Fill for a specific meeting note | |
└ /fill-participants all |
Scan and fill all meetings missing participants | |
| followup-todos | Extract action items as plain markdown bullets | |
├ /followup-todos <path> |
Extract from a specific meeting note | |
└ /followup-todos |
/note-status pending --step=todos |
|
| recap | Produce a recap from emails, Slack, Jira, and vault notes | |
├ /recap |
Recap current week (Monday through today) | |
└ /recap [dates] |
Recap a specific date range | today, yesterday, last week, 2026-01-01..2026-02-03 |
| sync-upstream-obsidianos | Pull structural updates from upstream ObsidianOS | |
├ /sync-upstream-obsidianos |
Preview and merge upstream updates | |
└ /sync-upstream-obsidianos preview |
Show what's new without merging | |
| note-status | Verify meeting notes are fully processed | |
├ /note-status <path> |
Check a specific note | |
├ /note-status [dates] |
Check notes in a date range | today, yesterday, last week, 2026-01-01..2026-02-03 |
├ /note-status all |
Check every meeting note | |
└ /note-status pending [dates] |
Filter to pending, prompt selection | --step=notes|cache|participants|todos |
| commit | Stage and commit with flexible intent parsing | |
├ /commit |
Staged files, or infer related changes | |
├ /commit <file or folder> |
Scope commit to a specific path | |
├ /commit <description> |
Infer scope from free-text intent | |
├ /commit amend [scope/description] |
Amend last commit (with optional scope or new message) | |
| └ (sequence mode) | Deferred — sub-skills skip, caller commits once at the end | |
| defuddle | Extract clean markdown from web pages with Defuddle CLI (prefer over raw fetch for articles & docs) | |
| json-canvas | Create and edit Obsidian JSON Canvas (.canvas) files |
|
| obsidian-bases | Create and edit Obsidian Bases (.base) — views, filters, formulas |
|
| obsidian-cli | Drive a running Obsidian app via the obsidian CLI (read/write/search, dev helpers) |
|
| obsidian-markdown | Obsidian Flavored Markdown — wikilinks, embeds, callouts, properties | |
| mail-transcripts | Drain Gmail AI-transcript notifications into meeting Notes: (gws) |
|
| organize-meetings | Triage Meetings/_inbox/ into the right subfolder via qmd + memory |
<path>, --auto |
| otter-fetch | Otter.ai transcript sub-skill (invoked by cache-notes / fill-participants) | |
| people-stubs | Batch-create Teams/People/@Name.md stubs from unresolved [[@*]] links |
--auto |
| onboard-person | Create/enrich a @Name.md from external sources (ATS / profile) |
<Name>, --candidate |
| last-1on1 | Flag overdue 1:1s by recency (Meetings.base OneOnOnes view) | <weeks>, @Name |
| vault-health | Audit unresolved links, orphans, deadends, sync conflicts | unresolved, orphans, deadends, sync, --fix-people |
| migrate-tags | Migrate body #hashtags to frontmatter tags: lists |
<path>, --dry-run, --strip-body |
| workspace-mode | Switch named Obsidian Workspace layouts | <name>, save <name> |
| sprint-retro | Synthesize a Sprint Retro draft from vault sources | <N>, <dates> |
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.
- 1mo ago First seen · 132 lines · 2,627 tokens per session scan A b1d8897205b4
obsidianos_work AGENTS.md is an instructions file published in the GitHub repository benoror/obsidianos_work (165 stars, last pushed 4mo ago), licensed MIT. It adds 2,627 tokens to every session, about $0.0105 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-08-30.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.