Borrowing it
Nothing to install: this file belongs to praveen-palanisamy/autodemo. 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/praveen-palanisamy/autodemo/main/AGENTS.mdgit clone --depth 1 https://github.com/praveen-palanisamy/autodemoWrote 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/praveen-palanisamy/autodemo/agents-md)<a href="https://agentmods.dev/instructions/praveen-palanisamy/autodemo/agents-md"><img src="https://agentmods.dev/badge/instructions/praveen-palanisamy/autodemo/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/praveen-palanisamy/autodemo/agents-md"><img src="https://agentmods.dev/badge/instructions/praveen-palanisamy/autodemo/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.00331 | $0.00331 |
| Opus 5 | $0.00166 | $0.00166 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
autodemo 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 12d 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
Agent instructions
Guidance for Cursor and other coding agents working in this repository.
After implementing a feature or fix
- Ensure the app is in a working state (run relevant scripts:
bun run typecheck,bun test,bun run site:buildwhen the site changed). - Review all related changes; stage every file that belongs to the work.
- Commit with a descriptive message — do not leave completed feature work uncommitted.
- Use conventional prefixes when appropriate:
feat:,fix:,docs:,chore:.
Push only when the user asks. Tags and releases follow the same “working state first, then tag” order.
Scripts over one-off commands
Prefer idempotent scripts in scripts/ (and package.json aliases) over ad-hoc shell one-liners so CI and local dev stay aligned.
Production and demos
- Changes must work in production deployment and local Firebase/emulator paths where applicable.
- Demo artifacts under
public/demos/are regenerated in CI; landing page video usesdata-src+ poster so autodemo captures stay poster-only (holdEmbeddedVideosin capture guards). - npm package:
@praveen-palanisamy/autodemo(CLI binary name remainsautodemo).
Code style
- Modular, SOLID, avoid huge single files.
- Match existing conventions in surrounding code.
- Use mermaid or kroki for diagrams in docs, not ASCII art.
- Do not add
Co-authored-bylines to commit messages.
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.
- 12d ago First seen · 30 lines · 331 tokens per session scan A 40339657f268
autodemo AGENTS.md is an instructions file published in the GitHub repository praveen-palanisamy/autodemo (3 stars, last pushed 2mo ago), licensed MIT. It adds 331 tokens to every session, about $0.0017 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).
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.
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).