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/hirokidaichi/noti/claude-mdgit clone --depth 1 https://github.com/hirokidaichi/notiWrote 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/hirokidaichi/noti/claude-md)<a href="https://agentmods.dev/instructions/hirokidaichi/noti/claude-md"><img src="https://agentmods.dev/badge/instructions/hirokidaichi/noti/claude-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.00373 | $0.00373 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
noti CLAUDE.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.
What it actually says
CLAUDE.md - noti project guidelines
Build & Development Commands
npm run dev- Run with watch modenpm run build- Build TypeScript to dist/npm run test- Run unit testsnpm run test:watch- Watch unit testsnpm run e2e- Run e2e testsnpm run lint- Run linternpm run fmt- Format codenpm run all-check- Run lint, build, and testsnpx vitest run src/path/to/specific.test.ts- Run specific test
Code Style Guidelines
- Formatting: 2 spaces indentation, 80 char line width, single quotes
- Error Handling: Use the ErrorHandler class with context strings
- Logging: Use the Logger singleton (info/error/debug/success methods)
- Imports: Organize in groups - standard lib, npm modules, local
- Naming: camelCase for variables/methods, PascalCase for classes
- Types: Define interfaces/types for all complex objects
- Testing: BDD style tests with Vitest (describe/it/expect)
- File Structure: Commands in src/commands/, utilities in src/lib/
Documentation
Japanese is the primary language for user-facing documentation and error messages
Agent Skill
notiをCLIツールとして使用する場合のドキュメントは .claude/skills/noti/ に配置されています：
SKILL.md- コマンドの使い方ガイドQUICKREF.md- クイックリファレンスexamples/- ワークフロー例
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 · 37 lines · 373 tokens per session scan A 56dca9ed6cea
noti CLAUDE.md is an instructions file published in the GitHub repository hirokidaichi/noti (5 stars, last pushed 5mo ago), licensed MIT. It adds 373 tokens to every session, about $0.0019 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.