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 instructions/onemore07/noteflowos/agents-mdgit clone --depth 1 https://github.com/OneMore07/NoteFlowOSWrote 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/onemore07/noteflowos/agents-md)<a href="https://agentmods.dev/instructions/onemore07/noteflowos/agents-md"><img src="https://agentmods.dev/badge/instructions/onemore07/noteflowos/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 | $0.01579 | $0.01579 |
| Opus 5 | $0.00790 | $0.00790 |
| Sonnet 5 | $0.00316 | $0.00316 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
NoteFlowOS 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 4d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions — NoteFlowOS
NoteFlowOS is an AI-powered knowledge management system built on Obsidian. It follows a structured folder model with a weekly journal workflow at its core. This file is read by Claude Code, OpenAI Codex, GitHub Copilot, Cursor, 通义千问 (Tongyi), Kimi, MiniMax, and other AI coding assistants.
1 Directory Structure
00_Inbox/ — Capture zone: clippings, quick notes, ideas
10_Journal/
├── 00_YEAR/ — Yearly review files
└── 01_WEEK/ — Weekly todo + weekly report pairs
20_Projects/ — Active deliverables: analyses, PRDs, reports
30_Wiki/
├── Articles/ — Deep-dive topics (AI-compiled from sources)
└── Concepts/ — Atomic concept definitions
40_Sources/
└── Feeds/ — Raw feeds, newsletters, clippings (append-only)
99_System/
├── 模板/ — Note templates
└── skills/ — Skill catalog and system docs
skills/ — Skill definition files
Knowledge flow: 00_Inbox → 40_Sources → 20_Projects → 30_Wiki
2 Frontmatter Rules
Every note must include type and created. Never leave a blank line between --- and the first frontmatter field.
---
type: <see enum below>
created: YYYY-MM-DD
---
Type Enum
| type | location | purpose |
|---|---|---|
inbox |
00_Inbox/ | unprocessed capture |
project |
20_Projects/ | active deliverable |
article |
30_Wiki/Articles/ | deep-dive topic |
concept |
30_Wiki/Concepts/ | atomic concept |
insight |
20_Projects/ or 30_Wiki/ | key finding |
weekly-todo |
10_Journal/01_WEEK/ | weekly task list |
weekly-report |
10_Journal/01_WEEK/ | weekly summary |
yearly-report |
10_Journal/00_YEAR/ | annual review |
weekly-ai-summary |
10_Journal/01_WEEK/ | AI-curated digest |
source |
40_Sources/ | raw source material |
curation |
40_Sources/Feeds/ | curated news/product digest |
index |
folder root | folder index file |
system |
99_System/ | system config/rules |
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.
- 4d ago First seen · 171 lines · 1,579 tokens per session scan A ecdc70706b86
NoteFlowOS AGENTS.md is an instructions file published in the GitHub repository OneMore07/NoteFlowOS (10 stars, last pushed 3mo ago), licensed MIT. It adds 1,579 tokens to every session, about $0.0079 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 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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.