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/keskinonur/shelfgap/agents-mdgit clone --depth 1 https://github.com/keskinonur/shelfgapWrote 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/keskinonur/shelfgap/agents-md)<a href="https://agentmods.dev/instructions/keskinonur/shelfgap/agents-md"><img src="https://agentmods.dev/badge/instructions/keskinonur/shelfgap/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.01736 | $0.01736 |
| Opus 5 | $0.00868 | $0.00868 |
| Sonnet 5 | $0.00347 | $0.00347 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
shelfgap 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 5d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShelfGap repository instructions
Mission
Build ShelfGap, an evidence-backed buyer decision simulator for small e-commerce merchants.
A merchant supplies normalized offer facts and buyer profiles or selects the built-in fictional sample. ShelfGap compares the merchant product and offer against exact-product resellers and alternative products. It evaluates them from several buyer perspectives, explains why the merchant wins or loses, and recommends the smallest feasible merchandising actions that could improve selectability.
The product must never claim guaranteed sales uplift, market share, or the globally lowest price.
Non-negotiable product principles
- Separate
Product,Offer, andBuyerContext. - Treat public listing data as time-sensitive evidence, not permanent truth.
- Mark every extracted value as
observed,inferred, orunknown. - Preserve source URL, evidence snippet, observation timestamp, and confidence.
- Distinguish exact-product offers from alternative products.
- Apply hard buyer requirements before preference scoring.
- Treat an unknown mandatory attribute as
uncertain, not false. - Calculate effective purchase cost from observable price, shipping, fees, and immediately usable discounts.
- Apply membership benefits only when the buyer profile has that active membership.
- Explain every score using visible components.
- Generate recommendations only from computed choice gaps and cited evidence.
- Require merchant approval before any simulated or real change.
- Keep fictional brands and neutral marketplace labels in the built-in demo.
- A more specific category recommendation must remain truthful and taxonomically valid.
Scope discipline
P0:
- Built-in fictional demo with no API key and no network dependency.
- Real user-supplied offer and buyer-profile analysis with no network dependency.
- Four buyer profiles plus a custom profile editor.
- Exact-offer and alternative-product comparisons.
- Deterministic eligibility, scoring, win-rate, gap analysis, and action cards.
- Before/after simulation for approved actions.
- Unit, integration, and one happy-path browser test.
- Clear README and demo instructions.
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.
- 5d ago First seen · 212 lines · 1,736 tokens per session scan A 7a04dffdf2f9
shelfgap AGENTS.md is an instructions file published in the GitHub repository keskinonur/shelfgap (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,736 tokens to every session, about $0.0087 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
opik copilot-instructions.md
Copilot instructions for comet-ml/opik, covering copilot code review instructions, project overview, 1. git workflow & branch management, branch naming convention and commit message standards.
instructor CLAUDE.md
Claude Code instructions for 567-labs/instructor, covering claude.md, instructor development guide, commands, installation & setup and code style guidelines.
openagent CLAUDE.md
Claude Code instructions for the-open-agent/openagent, covering claude.md, commands, architecture, backend (go / beego) and frontend (react).
gptme AGENTS.md
AGENTS.md instructions for gptme/gptme, covering agent instructions for gptme, git workflow, code style, testing and project structure.
GPT-RAG copilot-instructions.md
Copilot instructions for Azure/GPT-RAG, covering repository development and release instructions, branching strategy, default behavior, feature development workflow and branch creation.
AstrBot copilot-instructions.md
Copilot instructions for AstrBotDevs/AstrBot, covering astrbot development instructions, working effectively, bootstrap and install dependencies, running the application and dashboard build (vue.js/node.js).