Borrowing it
Nothing to install: this file belongs to Aptica-Solutions/a-mcp-runmeter. 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/Aptica-Solutions/a-mcp-runmeter/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Aptica-Solutions/a-mcp-runmeterWrote 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/aptica-solutions/a-mcp-runmeter/copilot-instructions)<a href="https://agentmods.dev/instructions/aptica-solutions/a-mcp-runmeter/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/aptica-solutions/a-mcp-runmeter/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.1 | $0.00679 | $0.00679 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
a-mcp-runmeter 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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
Read _engineer/ENGINEER-README.md for full project conventions and guardrails.
This file is a Copilot-specific summary. MCP servers are configured in .vscode/mcp.json.
ONBOARDING GATE — Read This First
Canonical template repository exception
Before applying this gate, determine whether the current checkout is the canonical template source. Both conditions must be true:
.is-template-repoexists in the repository root.git remote get-url originidentifiesAptica-Solutions/a-repo-templateor the legacyszeltneraptica/repo-templateGitHub repository.
This read-only check is permitted before onboarding. If both conditions are true,
the onboarding gate and the requirement to read AI-TASKS.md do not apply;
template review, maintenance, and validation may proceed without project onboarding
artifacts. Never rely on the marker alone because GitHub copies it into newly
created repositories until initialization removes it.
Do not write code, create files, plan architecture, run scripts, or make any project decisions until ONBOARDING.md exists in the project root and the user has confirmed it is accurate.
If ONBOARDING.md is missing or empty:
"ONBOARDING.md not found. Complete the survey in
_engineer/ONBOARDING.template.mdand save it asONBOARDING.mdbefore I can begin any project work."
If ONBOARDING.md exists but has not been confirmed this session, ask once:
"Is ONBOARDING.md current and accurate? (yes to confirm / describe what changed)"
Project Context
TODO: Describe the project domain, tech stack, and primary users.
Code Conventions
- Business logic in
services/— never in routes or components - Routes handle HTTP only
- Validation in
middleware/ - Config from environment variables — never hardcoded
- TypeScript strict mode
- Structured JSON logging with correlation IDs
Security — Always
- Never suggest hardcoded credentials, tokens, API keys, or connection strings
- Secrets belong in
.env(local) or Key Vault (deployed) — always via env vars - Validate all external inputs
- Flag any code that could expose PHI, PII, or credentials
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.
- 6d ago First seen · 81 lines · 679 tokens per session scan A a2b173553426
a-mcp-runmeter copilot-instructions.md is an instructions file published in the GitHub repository Aptica-Solutions/a-mcp-runmeter (0 stars, last pushed 1mo ago), licensed MIT. It adds 679 tokens to every session, about $0.0034 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-09-01.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.