What is vastai-host-mcp readme.instructions.md?

Project-specific rules for maintaining the main README.md file, the front page of a code repository. They cover badges, links, and information that should appear in the README.

They guide updates to README badges, license details, pull-request links, tags, and build-status information.

They keep the project’s main documentation consistent with its repository and status information.

How Cogni-AI-OU/vastai-host-mcp configures GitHub Copilot

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/Cogni-AI-OU/vastai-host-mcp/main/.github/instructions/readme.instructions.md

Clone the repo

git clone --depth 1 https://github.com/Cogni-AI-OU/vastai-host-mcp

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/cogni-ai-ou/vastai-host-mcp/readme/github.svg)](https://agentmods.dev/instructions/cogni-ai-ou/vastai-host-mcp/readme)

Your own site

<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.

Your own site · 80×15

<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>

Per session 729 This file is loaded in full into every session.

When invoked 729 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00292	$0.00292
Sonnet 5.5	$0.00146	$0.00146
Haiku 4.5	$0.00073	$0.00073

Measured 2mo ago against content hash be19c12d91cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.github/instructions/readme.instructions.md · 66 lines

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 LICENSE file 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.:

Read the full file on GitHub · 66 lines

Changes

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.

2mo ago First seen · 66 lines · 729 tokens per session scan A be19c12d91cb

Subscribe to this mod's changes

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 29d ago), licensed MIT. It adds 729 tokens to every session, about $0.0029 per session on Opus 5.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.

vastai-host-mcp readme.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
vastai-host-mcp readme.instructions.mdCogni-AI-OU/vastai-host-mcp	Instructions file	0	29d ago	MIT	A	729	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

vastai-host-mcp: Instructions file for GitHub Copilot