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/kiransth77/aionmcp/copilot-instructionsgit clone --depth 1 https://github.com/kiransth77/aionmcpWrote 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/kiransth77/aionmcp/copilot-instructions)<a href="https://agentmods.dev/instructions/kiransth77/aionmcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kiransth77/aionmcp/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.01381 | $0.01381 |
| Opus 5 | $0.00691 | $0.00691 |
| Sonnet 5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
aionmcp 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AionMCP - Autonomous Go MCP Server
Project Overview
AionMCP is an autonomous Go-based Model Context Protocol (MCP) server that dynamically imports OpenAPI, GraphQL, and AsyncAPI specifications and exposes them as tools to agents. Features self-learning, context-awareness, and auto-documentation using Clean/Hexagonal architecture.
Project Structure
cmd/ # Application entry points
internal/core/ # Core business logic
internal/adapters/ # External integrations
internal/registry/ # Tool registration system
internal/selflearn/ # Learning and reflection engine
pkg/agent/ # Agent integration APIs
docs/ # Auto-generated documentation
data/feedback/ # Learning data storage
Core Libraries & Dependencies
- API Framework:
github.com/gin-gonic/gin - gRPC:
google.golang.org/grpc - Plugin System:
github.com/hashicorp/go-plugin - Configuration:
github.com/spf13/viper - Logging:
go.uber.org/zap - Storage:
github.com/boltdb/bolt,github.com/dgraph-io/badger - Task Queue:
github.com/hibiken/asynq - Metrics:
github.com/prometheus/client_golang
MCP Protocol Implementation
Core interfaces follow this pattern:
type Tool interface {
Name() string
Description() string
Execute(input any) (any, error)
}
type ToolRegistry struct {
mu sync.RWMutex
tools map[string]Tool
}
MCP envelope format:
{
"protocol": "MCP/1.0",
"type": "tool_call",
"tool": "openapi.petstore.listPets",
"args": { "limit": 10 },
"context": { "session": "abc123" }
}
Development Iterations
Iteration 0: Project Scaffolding
Goal: Base MCP server structure
Outputs: cmd/server/main.go, internal/core/server.go, registry stub, docs/README.md, docs/architecture.md
Iteration 1: Spec Importer Layer
Goal: Multi-format API spec parsing
Outputs: pkg/importer/{openapi,graphql,asyncapi}.go, docs/spec_importer.md
Constraints: Go interfaces, hot-reloadable, cached tools
func ImportOpenAPI(path string) ([]Tool, error) {
spec, err := openapi3.NewLoader().LoadFromFile(path)
if err != nil { return nil, err }
var tools []Tool
for name, op := range spec.Paths {
tools = append(tools, NewOpenAPITool(name, op))
}
return tools, nil
}
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 · 156 lines · 1,381 tokens per session scan A 3dc82226cd8f
aionmcp copilot-instructions.md is an instructions file published in the GitHub repository kiransth77/aionmcp (3 stars, last pushed 5mo ago), licensed MIT. It adds 1,381 tokens to every session, about $0.0069 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
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).
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 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.
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.