Borrowing it
Nothing to install: this file belongs to jonigata/FramePlanner2. 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/jonigata/FramePlanner2/sns_main/AGENTS.mdgit clone --depth 1 https://github.com/jonigata/FramePlanner2Wrote 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/jonigata/frameplanner2/agents-md)<a href="https://agentmods.dev/instructions/jonigata/frameplanner2/agents-md"><img src="https://agentmods.dev/badge/instructions/jonigata/frameplanner2/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.00814 | $0.00814 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
FramePlanner2 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 yesterday.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/: Svelte 4 + TypeScript app code. Key areas:lib/(shared logic),stores/,utils/, feature folders (e.g.,bookeditor/,filemanager/,notebook/). Entry points:main.ts,App.svelte.public/: Static assets bundled by Vite.test/andtestdata/: Vitest helpers and fixtures (test/setup.ts,test/helpers.ts).dist/: Build output. Do not edit.- Config:
vite.config.ts,tsconfig*.json,tailwind.config.cjs,postcss.config.cjs,.env*,wrangler.toml,firebase.json.
Build, Test, and Development Commands
npm run dev: Start Vite dev server.npm run dev-https: Local HTTPS dev usingvite.https.config.tsand bundled certs.npm run build: Typecheck and bundle todist/.npm run preview: Serve the production build locally.npm run check: Runsvelte-checktype diagnostics.npm run vitest(ornpx vitest --run): Run unit tests.- テスト実行時は
npx tsc --noEmit && npm run vitest -- --runのように型チェックも併せて行うこと。 - Deploy:
npm run deploy(publishes via Cloudflare Pages only onsns_main).
Coding Style & Naming Conventions
- TypeScript, 2-space indentation, semicolons optional but be consistent.
- Svelte components: PascalCase (
FramePanel.svelte). Utilities/stores: camelCase files (fileSystem.ts,uiStore.ts). - Path aliases:
$bookTypes/*→src/lib/book/types/*,$protocolTypes/*→src/utils/edgeFunctions/types/*. - Keep UI in
.svelte, business logic insrc/lib/**, and side effects insrc/utils/**. - Styling via Tailwind/PostCSS; prefer utility classes over inline styles.
Testing Guidelines
- Framework: Vitest with jsdom and polyfills in
test/setup.ts(import in specs as needed). - Location: place specs under
test/or alongside code as*.test.ts. - Write deterministic tests; mock browser APIs and storage via helpers in
test/helpers.ts. - Example:
npx vitest --run --reporter=verbose.
Commit & Pull Request Guidelines
- Commit style: imperative mood; optional Conventional Commits (
feat:,fix:,chore:). Example:feat(book): add multi-image reference support. - Before PR: run
npm run check,npm run build, and tests. - PRs: include clear description, linked issues (
Closes #123), and screenshots/GIFs for UI changes. - Branching: target
sns_mainwhen preparing a release. Deploys run fromsns_mainvianpm run deploy.
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.
- yesterday First seen · 50 lines · 814 tokens per session scan A 25bbd1dd9f69
FramePlanner2 AGENTS.md is an instructions file published in the GitHub repository jonigata/FramePlanner2 (43 stars, last pushed 15d ago), licensed MIT. It adds 814 tokens to every session, about $0.0041 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-09-04.
Other instructions, from other repositories
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.
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).
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).
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.
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.