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/schplitt/mc8yp/agents-mdgit clone --depth 1 https://github.com/schplitt/mc8ypWhat 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.13452 | $0.13452 |
| Opus 5 | $0.06726 | $0.06726 |
| Sonnet 5 | $0.02690 | $0.02690 |
| Haiku 4.5 | $0.01345 | $0.01345 |
Grade A, and why
mc8yp 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 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.
How it starts
The opening of the file, as written. The whole thing — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
mc8yp is a Cumulocity IoT MCP server.
The project exposes a single code-mode tool to AI agents instead of a large fixed toolset:
codemoderuns an async JavaScript function in a sandbox where API discovery, documentation search, and typed live API calls are all available as globals:codemode.search(query)/codemode.describe(target?)— ranked method search and on-demand TypeScript interface rendering over operations derived from the OpenAPI specsdocs.search(query, opts?)/docs.read(id)— MiniSearch-backed fuzzy full-text search over spec prose (tag docs like query-language grammars, info blocks, operation/parameter descriptions)c8y(core, always present) plus one namespace per service available on the tenant (e.g.dtm) — one typed method per derived operation. Namespaces are the COMPLETE sandbox surface: there is no raw-request escape hatch, and the backing protocol (OpenAPI vs MCP) is deliberately invisible to the agent- services that declare
exposeMcpServersin their manifest are wrapped from their MCP server instead (one typed method per MCP tool) — MCP is preferred over the OpenAPI spec when a service has both, with a per-connection opt-out (mc8yp-no-mcpheader /noMcpquery /--no-mcpCLI flag) that falls back to the spec - external MCP servers supplied by the connection itself (
mc8yp-mcp-serverheader, repeatable, JSON per entry;--mcp-serverCLI flag) get a namespace too — absolute URL, their own credentials, tenant-independent, scoped to that connection/session sandbox(server mode only, opt-in — disabled by default) — an in-memory shell + virtual filesystem (just-bash, core shell only:jq/awk/grep/sed/sort/sqlite3, no network, no host FS) for wrangling fetched data. Mirrors Flue'sSandboxApiplus an mc8yp-onlyclear(). One sandbox per MCP session (persists across codemode calls, keyed byctx.sessionId), idle-evicted after 15 minutes; nothing touches disk. A connection only gets it after opting in via themc8yp-enable-sandboxheader /enableSandboxquery param — a general-purpose shell + virtual FS is a bigger blast radius than any single typed API call, so it must be explicitly requested. CLI mode never exposes it regardless — local harnesses bring their own file I/O. Backed by a swappable adapter so the provider can change later.
statusis available only in CLI mode: it lists the active tenant, stored credentials, and the API namespaces currently visible. It accepts{ refresh: true }to force a fresh API discovery on demand (noop when no tenant is active). Server mode has no in-protocol equivalent yet — use thePOST /refresh-apisHTTP route for ops-driven refresh; an in-protocol server-side flow will land in a separate PR.
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.
- 2d ago First seen · 414 lines · 13,452 tokens per session scan A 76d60f333e8a
mc8yp AGENTS.md is an instructions file published in the GitHub repository schplitt/mc8yp (6 stars, last pushed 3d ago), licensed MIT. It adds 13,452 tokens to every session, about $0.0673 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
cumulocity-dynamic-mapper AGENTS.md
Instructions for Cumulocity-IoT/cumulocity-dynamic-mapper, covering cumulocity dynamic mapper — agent guidelines, module structure, documentation map, quick commands and backend (java 21, maven).
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.
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.
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).