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/metrostar/comet/agents-mdgit clone --depth 1 https://github.com/MetroStar/cometWhat 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.00397 | $0.00397 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 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 2d 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.
- 2d 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 (27 stars, last pushed 4d ago), licensed Apache-2.0. It adds 397 tokens to every session, about $0.0020 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-30.
Other instructions, from other repositories
heroui CLAUDE.md
Claude Code instructions for heroui-inc/heroui, covering claude.md, repository overview, key technical stack, development commands and core development commands.
tiny-vue AGENTS.md
Instructions for opentiny/tiny-vue, covering agents.md, 项目概述, 关键目录结构, 环境要求 and 核心命令.
figma-console-mcp CLAUDE.md
Instructions for southleft/figma-console-mcp, covering figma console mcp, build & test, release process, known issues and architecture.
ShipSwift AGENTS.md
Instructions for signerlabs/ShipSwift, covering agents.md, project overview, directory structure, naming conventions and dependency rules.
starwind-ui AGENTS.md
Instructions for starwind-ui/starwind-ui, covering agents.md, project shape, useful commands and contribution conventions.
unity-ui-toolkit-design-system AGENTS.md
Instructions for sinanata/unity-ui-toolkit-design-system, covering agents.md, what this project is, golden rules (do not violate), use the design system in your project and repository layout.