Borrowing it
Nothing to install: this file belongs to Cogni-AI-OU/vastai-host-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Cogni-AI-OU/vastai-host-mcp/main/.github/instructions/readme.instructions.mdgit clone --depth 1 https://github.com/Cogni-AI-OU/vastai-host-mcpWrote 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/cogni-ai-ou/vastai-host-mcp/readme)<a href="https://agentmods.dev/instructions/cogni-ai-ou/vastai-host-mcp/readme"><img src="https://agentmods.dev/badge/instructions/cogni-ai-ou/vastai-host-mcp/readme/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/cogni-ai-ou/vastai-host-mcp/readme"><img src="https://agentmods.dev/badge/instructions/cogni-ai-ou/vastai-host-mcp/readme.svg" alt="Reviewed on agentmods" width="80" 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.00729 | $0.00729 |
| Opus 5 | $0.00365 | $0.00365 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
vastai-host-mcp readme.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 10d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Instructions
Badge Guidance
- Use dynamic badges from shields.io; keep them on one line below the title.
- Include a PR reviews badge using reference links, e.g.:
[![PR Reviews][pr-reviews-image]][pr-reviews-link][pr-reviews-image]: https://img.shields.io/github/issues-pr/{org}/{repo}?label=PR+Reviews&logo=github[pr-reviews-link]: https://github.com/{org}/{repo}/pulls
- Include a license badge linked to TLDRLegal using reference links, e.g.:
[![License][license-image]][license-link][license-image]: https://img.shields.io/badge/License-MIT-blue.svg[license-link]: https://tldrlegal.com/license/mit-license
- If project has any tags, add a tags badge:
[![Tags][tags-image]][tags-link][tags-image]: https://img.shields.io/github/tag/{org}/{repo}.svg?logo=github[tags-link]: https://github.com/{org}/{repo}/tags
- If project uses GitHub Actions, include a build status badge:
[![Status][gha-image-{workflow}-{branch}]][gha-link-{workflow}-{branch}][gha-link-{workflow}-{branch}]: https://github.com/{org}/{repo}/actions?query=workflow%3A{name}%3A{branch}[gha-image-{workflow}-{branch}]: https://github.com/{org}/{repo}/workflows/{name}/badge.svg
- Include project status badges as available (update workflow names as needed):
- Optional: Docs/site badge if a published site exists.
Structure
- Start with a concise summary of the project purpose and scope.
- Add a "Getting Started" section covering prerequisites, setup, and a minimal quickstart.
- Add a "Development" section for local workflows (e.g.,
pre-commit run --all-files, running tests). - Add a "Project Layout" section describing key directories (e.g.,
.github/instructions/,.github/agents/). - Add a "Contributing" section summarizing contribution expectations and linking to any contributing guide if present.
- Add a "License" section that links to the local
LICENSEfile if it exists in the repository, otherwise link to the TLDRLegal page (e.g. https://www.tldrlegal.com/license/mit-license) for the project's license. - For lengthy READMEs, include a Table of Contents using a TOC block, e.g.:
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.
- 10d ago First seen · 66 lines · 729 tokens per session scan A be19c12d91cb
vastai-host-mcp readme.instructions.md is an instructions file published in the GitHub repository Cogni-AI-OU/vastai-host-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 729 tokens to every session, about $0.0036 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
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.
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 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.
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).