Borrowing it
Nothing to install: this file belongs to meghal86/promptsonar. 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/meghal86/promptsonar/main/AGENTS.mdgit clone --depth 1 https://github.com/meghal86/promptsonarWrote 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/meghal86/promptsonar/agents-md)<a href="https://agentmods.dev/instructions/meghal86/promptsonar/agents-md"><img src="https://agentmods.dev/badge/instructions/meghal86/promptsonar/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.02275 | $0.02275 |
| Opus 5 | $0.01137 | $0.01137 |
| Sonnet 5 | $0.00455 | $0.00455 |
| Haiku 4.5 | $0.00228 | $0.00228 |
Grade A, and why
promptsonar 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 6d 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PromptSonar Agent Instructions
This is the canonical shared instruction file for coding agents working in this repository, including Codex and Claude Code. Tool-specific files may add local supplements, but they must not contradict this file.
PromptSonar is a TypeScript monorepo using npm workspaces. It is a local-first static security scanner for prompts, agent instructions, and MCP configs.
Operating Principles
- Prefer small, reviewable diffs and keep behavior deterministic.
- PromptSonar is intentionally offline and makes zero LLM calls.
- When changing rules or engine behavior, add or update tests so the change is provable and non-regressive.
- Avoid introducing new heavyweight dependencies unless there is a clear need.
- Do not commit secrets. Use
.envand keep.envout of git.
Repo Layout
packages/core- scanning engine and rulespackages/cli- CLI wrapperpackages/dashboard- playground UIpackages/claude-code- Claude Code adapterpackages/cursor-extension- Cursor extensionpackages/vscode-extension- VS Code extensionaction- GitHub Action wrapperdocs/- documentation and release notestests//packages/*/tests- test suites, varying by package
Common Commands
- Install:
npm ci - Build:
npm run build - Test:
npm test - Lint:
npm run lint - Smoke test:
npm run smoke:features - MCP benchmark:
npm run benchmark:mcp
Change Workflow
- Identify the package or packages impacted.
- Add or adjust tests first when feasible, especially for rule and engine behavior changes.
- Implement the smallest scoped change.
- Run the narrowest relevant verification, such as
npm test --workspace packages/core, then broader relevant checks. - Inspect the final diff before reporting completion.
Coding Agent Operating Rules
Read Before Editing
Before changing code:
- read the relevant implementation
- read nearby tests
- inspect relevant types, schemas and documentation
- trace the current behavior
- identify the root cause before proposing a fix
- check whether similar behavior already exists elsewhere in the repository
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.
- 6d ago First seen · 367 lines · 2,275 tokens per session scan A 942ec3fbd879
promptsonar AGENTS.md is an instructions file published in the GitHub repository meghal86/promptsonar (5 stars, last pushed 7d ago), licensed MIT. It adds 2,275 tokens to every session, about $0.0114 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
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.