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/ideabosque/mcp_skill_provider/agents-mdgit clone --depth 1 https://github.com/ideabosque/mcp_skill_providerWrote 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/ideabosque/mcp_skill_provider/agents-md)<a href="https://agentmods.dev/instructions/ideabosque/mcp_skill_provider/agents-md"><img src="https://agentmods.dev/badge/instructions/ideabosque/mcp_skill_provider/agents-md.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 | $0.00629 | $0.00629 |
| Opus 5 | $0.00315 | $0.00315 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
mcp_skill_provider 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Notes for mcp_skill_provider
Project Basics
- Python project managed via
pyproject.toml(setuptools backend). - Package name:
mcp_skill_provider. - No CLI entrypoint — installed as a package and loaded by
mcp_daemon_engine. - Dev dependencies:
pytest,black,ruff. - Uses
pyhumps(nothumps) fordecamelize— seepyproject.tomlcomment.
Architecture
mcp_skill_provider is a flat composition of mixins that expose Harness Engineering skill tools through mcp_daemon_engine.
mcp_skill_provider/
__init__.py # Exports MCPSkillProvider + MCP_CONFIGURATION
mcp_skill_provider.py # Facade class composing mixins
mcp_configuration.py # MCP_CONFIGURATION dict (tools + inputSchema)
graphql_client.py # GraphQLClient → HTTP/2 to harness_engineering_engine
graphql_backed_processor.py # Root base: logger, setting, graphql_client
skill_mixin.py # search_skills, get_skill
command_mixin.py # run_command
error_handler.py # Decorators + skill-specific ErrorCode constants
How it connects to mcp_daemon_engine
mcp_daemon_engine loads MCP modules via the loadMcpConfiguration GraphQL mutation. The MCP_CONFIGURATION dict declares:
- Module name:
mcp_skill_provider - Class:
mcp_skill_provider.mcp_skill_provider.MCPSkillProvider - Three functions:
search_skills,get_skill,run_command
GraphQLClient.execute_query() posts to the module's configured graphql_modules.harness_engineering.endpoint with either a silvaengine_gateway JWT Bearer token (preferred) or x-api-key header.
Code Style
- Follow SilvaEngine conventions:
__future__import,__author__ = "bibow"header, type hints. - All GraphQL calls go through
GraphQLClient.execute_query()— never importharness_engineering_enginedirectly. - Field names returned from GraphQL are camelCase; the mixins call
humps.decamelize()to normalize to snake_case before returning to the MCP caller. - Errors use the
error_handlerdecorator pattern:@handle_errors(operation_name="...")on every public method, withpropagate_error_if_present()used to forward backend errors.
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 · 53 lines · 629 tokens per session scan A 3ccf94617dc3
mcp_skill_provider AGENTS.md is an instructions file published in the GitHub repository ideabosque/mcp_skill_provider (0 stars, last pushed 8d ago), licensed MIT. It adds 629 tokens to every session, about $0.0031 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).
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.
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).
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.