mycommandmcp copilot-instructions.md

Project-specific instructions for MyCommandMCP, a Rust server that turns command-line programs into tools an AI agent can use. It also defines file or web resources and reusable prompts through YAML configuration.

In plain words
What is it for?
Use it when developing or maintaining MyCommandMCP, including Rust code, command-line tool integrations, resources, prompts, and configuration.
Why use it?
It gives the agent the project's technology choices, coding rules, documentation sources, and required workflow in one place.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/sevir/mycommandmcp/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/sevir/mycommandmcp

Made for: GitHub Copilot.

Per session 419 This file is loaded in full into every session.
When invoked 419 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00419 $0.00419
Opus 5 $0.00210 $0.00210
Sonnet 5 $0.00084 $0.00084
Haiku 4.5 $0.00042 $0.00042

Measured 2d ago against content hash 2c624544b522, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mycommandmcp 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 2d 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.

.github/copilot-instructions.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MyCommandMCP

Project Overview

This is a project of MCP server (Model Context Protocol) built in Rust, for eto enable any command line app into a MCP tool. Also you can define MCP Resources as files or urls and MCP Prompts with a simple yaml configuration. Please review README.md and other .md files of the root folder of the project for more references.

Technology Stack

  • Language: Rust
  • Framework: Rust
  • Database: none

Development Guidelines

Code Style

  • Use Rust for all code
  • Follow Rust conventions for server/client component separation
  • Ensure consistent use of Rust features and idioms
  • Search in Google (Serper) if it is necessary for more information about general concepts.
  • Check with Context7 the documentation for any specific guidelines.
  • Ask for help if you are stuck.
  • Use Serena tools for search symbols, edit code or refactor.
  • Use Remembrances tools always at the beginning of a task for searching any useful information and at the end for summarizing what you have learned.
  • Saves into knowledge base or memories all relevant information about the project changes of interest for the future tasks.
  • If you have a complex task, break it down into smaller steps, use Sequential thinking and steps list for the process
  • Fetch any relevant information from urls of the context task for updated context
  • If you need build or running tests use Terminal.
  • Always add tests for any new functionality.

Testing

  • Run xc check for linting and type checking and launching tests

Deployment

  • Run xc build for building the project and review the output for any errors.

Troubleshooting

Common Issues

  • Type Errors: Check readonly props and proper Rust types

Debug Tips

  • Check terminal errors running tests or build

Contributing

When making changes:

  1. Follow existing code patterns
  2. Update documentation as needed
  3. Test thoroughly before committing
  4. Consider performance and accessibility implications

Read the full file on GitHub · 63 lines

Changes

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.

  1. 2d ago First seen · 63 lines · 419 tokens per session scan A 2c624544b522

Subscribe to this mod's changes

mycommandmcp copilot-instructions.md is an instructions file published in the GitHub repository sevir/mycommandmcp (5 stars, last pushed 9mo ago), licensed MIT. It adds 419 tokens to every session, about $0.0021 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens