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/johnpapa/shopathome/copilot-instructionsgit clone --depth 1 https://github.com/johnpapa/shopathomeWrote 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/johnpapa/shopathome/copilot-instructions)<a href="https://agentmods.dev/instructions/johnpapa/shopathome/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/johnpapa/shopathome/copilot-instructions.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 | $0.01356 | $0.01356 |
| Opus 5 | $0.00678 | $0.00678 |
| Sonnet 5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
shopathome copilot-instructions.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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — Shop at Home
Language & Framework Conventions
JavaScript / TypeScript
- Use
constandlet— nevervar. - Prefer arrow functions for callbacks and inline functions.
- Use template literals for string interpolation.
- Use
async/awaitover raw Promises where possible. - TypeScript (Angular and Svelte apps): use explicit types for function parameters and return values. Avoid
any.
Angular (angular-app)
- Follow Angular CLI conventions: one component per file,
*.component.ts/*.service.ts/*.module.tssuffixes. - Use NgRx for state management — actions, reducers, effects, selectors follow the NgRx pattern in
src/app/. - Use Angular's dependency injection for services.
- Router configuration lives in
src/app/router.ts. - Templates use Angular template syntax with structural directives (
*ngIf,*ngFor). - Lint with TSLint (
tslint.jsonatsrc/tslint.json).
React (react-app)
- Class components are not used — prefer functional components.
- State management uses Redux with Redux-Saga for side effects (see
src/store/). - Follow the Airbnb ESLint configuration (
.eslintrc.jsonextendsreact-app). - Format with Prettier (
.prettierrc). - Router uses
react-router-domv6.
Svelte (svelte-app)
- Use TypeScript in Svelte components (
<script lang="ts">). - Styling uses SCSS imported globally from
src/styles.scss. - Build with Vite (
vite.config.ts). - Check types with
npm run check(svelte-check). - Store module in
src/store/— uses Svelte writable stores.
Vue (vue-app)
- Single-File Components (
.vue) with<template>,<script>,<style>sections. - State management via Vuex (
src/store/). - Routing via Vue Router (
src/router.js). - Follow Vue ESLint + Airbnb + Prettier rules (
.eslintrc.js). - Component filenames use kebab-case.
API — Azure Functions (api/)
- Each function is a directory with
function.json(bindings) andindex.js(handler). - Handlers receive
(context, req)and set response viacontext.res. - Shared data logic lives in
api/shared/. - Routes are defined declaratively in
function.json, not in code.
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.
- 4d ago First seen · 104 lines · 1,356 tokens per session scan A 7169b3be33ee
shopathome copilot-instructions.md is an instructions file published in the GitHub repository johnpapa/shopathome (135 stars, last pushed 1mo ago), licensed MIT. It adds 1,356 tokens to every session, about $0.0068 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
kolibri copilot-instructions.md
Copilot instructions for public-ui/kolibri, covering github copilot instructions for kolibri repository, kolibri overview, essential setup commands, 1. install node.js 22 and 2. enable pnpm.
kolibri AGENTS.md
AGENTS.md instructions for public-ui/kolibri, covering agent instructions, handling hints, 🚨 format-first rule, semantic versioning and project structure.
elements AGENTS.md
AGENTS.md instructions for NVIDIA/elements, covering agents.md, instruction precedence for agents, repository overview, environment requirements and common commands.
elements CLAUDE.md
Claude Code instructions for NVIDIA/elements, a project described as: NVIDIA Design System and UI Agent Harness for AI/ML Factories, Robotics, and Autonomous Vehicles.
ag-charts AGENTS.md
AGENTS.md instructions for ag-grid/ag-charts, covering ai agent instructions, ambiguity and confidence, project overview, critical rules and pre-commit requirements.
ag-charts CLAUDE.md
Claude Code instructions for ag-grid/ag-charts, a project described as: AG Charts is a fully-featured and highly customizable JavaScript charting library. The professional choice for developers building enterprise applications.