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/provide-io/pyvider/claude-mdgit clone --depth 1 https://github.com/provide-io/pyviderWrote 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/provide-io/pyvider/claude-md)<a href="https://agentmods.dev/instructions/provide-io/pyvider/claude-md"><img src="https://agentmods.dev/badge/instructions/provide-io/pyvider/claude-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.00734 | $0.00734 |
| Opus 5 | $0.00367 | $0.00367 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
pyvider CLAUDE.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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Quick Commands
Task Runner (wrknv)
This project uses wrknv for task automation. All tasks can be run with we run <task>.
we tasks # List all available tasks
we run test # Run tests
we run test.coverage # Run with coverage report
we run test.parallel # Run tests in parallel
we run lint # Check code quality
we run lint.fix # Auto-fix linting issues
we run format # Format code
we run format.check # Check formatting without changes
we run typecheck # Run type checker
we run build # Build distribution
For complete task documentation, see wrknv.toml or run we tasks.
Environment Setup
# Install dependencies
uv sync
Pyvider CLI
# Core commands
pyvider --help # Show help
pyvider install # Install provider for Terraform
pyvider provide # Start provider server (default)
# Component management
pyvider components list # List all components
pyvider components show resource <name> # Show component schema
pyvider components diagnostics # Show discovery diagnostics
# Configuration & debugging
pyvider config show # Display current configuration
pyvider launch-context # Show how pyvider was launched
Key Patterns
Component Model
Pyvider uses a hub-based discovery system where components self-register via decorators:
@register_provider- Provider configuration@register_resource- CRUD resources@register_data_source- Read-only data@register_function- Callable functions@register_ephemeral_resource- Short-lived resources@register_list_resource- Listable resources for the ListResource RPC@register_state_store- Durable state-store backends@register_action- Provider-defined actions
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.
- 4d ago First seen · 95 lines · 734 tokens per session scan A 1d5740ef2e5d
pyvider CLAUDE.md is an instructions file published in the GitHub repository provide-io/pyvider (2 stars, last pushed today), licensed Apache-2.0. It adds 734 tokens to every session, about $0.0037 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.