Borrowing it
Nothing to install: this file belongs to PedroHSGuimaraes/nuvem-shop-mcp-server. 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/PedroHSGuimaraes/nuvem-shop-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/PedroHSGuimaraes/nuvem-shop-mcp-serverWrote 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/pedrohsguimaraes/nuvem-shop-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/pedrohsguimaraes/nuvem-shop-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/pedrohsguimaraes/nuvem-shop-mcp-server/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/pedrohsguimaraes/nuvem-shop-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/pedrohsguimaraes/nuvem-shop-mcp-server/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.00853 | $0.00853 |
| Opus 5 | $0.00426 | $0.00426 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
nuvem-shop-mcp-server 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 10d 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.
This is a copy
86% identical to musicbrainz-mcp-server copilot-instructions.md — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[byterover-mcp]
[byterover-mcp]
[byterover-mcp]
Byterover MCP Server Tools Reference
There are two main workflows with Byterover tools and recommended tool call strategies that you MUST follow precisely.
Onboarding workflow
Trigger this workflow only if users particularly ask you to start the onboarding process. You MUST follow these steps.
- ALWAYS USE byterover-check-handbook-existence first to check if the byterover handbook already exists. If not, You MUST call byterover-create-handbook to create the byterover handbook.
- If the byterover handbook already exists, first you MUST USE byterover-check-handbook-sync to analyze the gap between the current codebase and the existing byterover handbook.
- Then IMMEDIATELY USE byterover-update-handbook to update these changes to the byterover handbook.
- Next, you MUST run byterover-retrieve-knowledge to gather context and knowledge about the project before generating the handbook.
- During the onboarding, you MUST use byterover-list-modules FIRST to get the available modules, and then byterover-store-modules and byterover-update-modules if there are new modules or changes to existing modules in the project.
Planning workflow
Trigger this workflow when users require you to start an implementation plan, carry out bug fixes, or make a new feature to the project. You MUST follow these steps.
- If asked to continue an unfinished implementation, CALL byterover-retrieve-active-plans to find the most relevant active plan.
- CRITICAL PLAN PERSISTENCE RULE: Once a user approves a plan, you MUST IMMEDIATELY CALL byterover-save-implementation-plan to save it.
- Throughout the plan, you MUST run byterover-retrieve-knowledge several times to retrieve sufficient knowledge and context for the plan's tasks.
- In addition, you MUST run byterover-search-modules and byterover-update-modules if the tasks require or update knowledge about certain modules.
- MUST use byterover-update-plan-progress to mark tasks (and then the whole plan) as completed.
- Then, you might call byterover-store-knowledge to save knowledge and experience implemented throughout the plan or in important tasks.
- During the plan's implementation, you MUST frequently call byterover-think-about-collected-information and byterover-assess-context-completeness to make sure you're on the right track and gather sufficient context for the tasks.
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.
- 10d ago First seen · 36 lines · 853 tokens per session scan A 3cc9d990f7bc
nuvem-shop-mcp-server AGENTS.md is an instructions file published in the GitHub repository PedroHSGuimaraes/nuvem-shop-mcp-server (0 stars, last pushed 1y ago), licensed MIT. It adds 853 tokens to every session, about $0.0043 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to musicbrainz-mcp-server copilot-instructions.md, differing in 20 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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.
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).