Borrowing it
Nothing to install: this file belongs to desirecore/market. 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/desirecore/market/main/AGENTS.mdgit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/agents-md)<a href="https://agentmods.dev/instructions/desirecore/market/agents-md"><img src="https://agentmods.dev/badge/instructions/desirecore/market/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/desirecore/market/agents-md"><img src="https://agentmods.dev/badge/instructions/desirecore/market/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.00698 | $0.00698 |
| Opus 5.5 | $0.00279 | $0.00279 |
| Sonnet 5.5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
market 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- market CLAUDE.md — 95% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is a public marketplace. Every contribution must be reusable, customer-neutral, and safe to index publicly.
Public information boundary
- Never put a tenant, customer, prospect, partner, or other confidential identity in tracked files, paths, filenames, Agent, Team or Skill IDs, frontmatter, descriptions, examples, fixtures, memories, generated artifacts, or screenshots.
- Apply the same rule to Git metadata and collaboration text: branch names, commit subjects and bodies, PR or issue titles and bodies, comments, and review replies.
- Describe reusable capabilities with domain-neutral roles and entities. Put customer-specific prompts, facts, mappings, examples, data, and deployment settings only in private AgentFS homes, private repositories, or private runtime configuration.
- Do not add a real confidential token to a denylist, test fixture, documentation, or example. A literal denylist in a public repository creates a second leak.
External dependency disclosure
- A Skill, Agent or Team that relies on separately licensed, purchased, hosted, or
deployed third-party software must disclose that dependency in its discovery
description,
compatibilityfield, localized marketplace text, and execution instructions. - Distinguish an included connector or adapter Tool from the external product it accesses. Never imply that registering a Tool bundles, licenses, installs, pays for, or operates the third-party product.
- State the operator prerequisites, applicable licensing or usage terms, separate costs when relevant, connection readiness checks, and safe degraded behavior. If the dependency is unavailable, stop before the external call and never fabricate a successful result.
Required pre-publication check
Before committing or opening/updating a PR:
- Obtain the sensitive tokens through a private channel and keep them outside the repository.
- Scan the complete working tree, including hidden files while excluding
.git. - Scan new path names, branch names, commit subjects and bodies, and the proposed PR/issue/review text.
- Review examples semantically: changing a proper noun is insufficient when an example still exposes a customer-specific organization shape or private fact.
- Run the repository validation and translation-freshness checks documented in
README.md.
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.
- 1mo ago Changed · +4 tokens per session b13f7d285b22
- 1mo ago First seen · 70 lines · 694 tokens per session scan A 9728cedf1e35
market AGENTS.md is an instructions file published in the GitHub repository desirecore/market (2 stars, last pushed today), licensed MIT. It adds 698 tokens to every session, about $0.0028 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-31.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.