Borrowing it
Nothing to install: this file belongs to MetroStar/comet. 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/MetroStar/comet/main/AGENTS.mdgit clone --depth 1 https://github.com/MetroStar/cometWrote 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/metrostar/comet/agents-md)<a href="https://agentmods.dev/instructions/metrostar/comet/agents-md"><img src="https://agentmods.dev/badge/instructions/metrostar/comet/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/metrostar/comet/agents-md"><img src="https://agentmods.dev/badge/instructions/metrostar/comet/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.00397 | $0.00397 |
| Opus 5.5 | $0.00159 | $0.00159 |
| Sonnet 5.5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
comet 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 2mo 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
Comet
This project is a React with TypeScript Component Library based on USWDS. It is designed to provide a set of modular tools to accelerate developer productivity and simplify the use of Design Systems, particularly USWDS.
Project Structure
This project is built with the following tools and libraries:
- React with TypeScript
- Vite for managing React Development and Bundling
- Vitest for unit testing, do not use Jest
- USWDS for the primary Component Library
- Storybook code examples and documentation
Development Guidelines
- Use TypeScript for type safety.
- All components should include an
idprop. - Use arrow functions for components and hooks.
- Use functional components instead of class components.
- Components should return
React.ReactElement. - Use default exports for components.
- Use PascalCase for component names.
- Use kebab-case for file names and directories.
- New components should be added to their own directory and should include at least: component, stories, test, figma file, and index.
- New components should be exported from an
index.tsfile in their directory. - New components should be exported from the main
index.tsfile in the package. - New components should include jsdoc comments.
Styling Guidelines
- Use CSS for styling.
- Component level styling should be in a
.cssfile with the same name as the component.
Unit Testing
- Use Vitest for unit testing, never use Jest.
- Use React Testing Library for testing React components.
- Use 'test' instead of 'it' for test names.
Code Quality
- Use ESLint for code analysis.
- Use Prettier for code formatting.
Accessibility
- Ensure HTML is WCAG 2.1 AA and Section 508 compliant.
- Ensure HTML meets accessibility best practices for screen readers, keyboard navigation, and color contrast.
- Use semantic HTML and ARIA roles appropriately.
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.
- 2mo ago First seen · 51 lines · 397 tokens per session scan A 66a59c762b79
comet AGENTS.md is an instructions file published in the GitHub repository MetroStar/comet (29 stars, last pushed 8d ago), licensed Apache-2.0. It adds 397 tokens to every session, about $0.0016 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.