agentmods.dev

personal-copilot-instructions: Instructions file for GitHub Copilot

.github/instructions/copilot-readme.instructions.md

personal-copilot-instructions copilot-readme.instructions.md is an instructions file for GitHub Copilot from Ismola/personal-copilot-instructions. It costs 573 tokens per session, scanned A, original, MIT.

A set of GitHub Copilot instructions for creating or updating a project's README file. GitHub Copilot is an AI coding assistant, and a README explains what a project does and how to use it.

In plain words
What is it for?
Use it to inspect a project and produce an accurate README with relevant sections such as structure, setup, commands, or environment variables.
Why use it?
It prevents documentation from describing files, settings, or commands that are not actually present, while preserving useful existing content.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is Ismola/personal-copilot-instructions's own configuration. It tells GitHub Copilot how to work on personal-copilot-instructions itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything personal-copilot-instructions configures →

not rated 1repo 1y ago A scan 573 tokens original MIT
View source ↗ Ismola/personal-copilot-instructions
Reuse

Borrowing it

Nothing to install: this file belongs to Ismola/personal-copilot-instructions. 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/Ismola/personal-copilot-instructions/main/.github/instructions/copilot-readme.instructions.md
Clone the repo
git clone --depth 1 https://github.com/Ismola/personal-copilot-instructions

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.

agentmods badge for personal-copilot-instructions copilot-readme.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ismola/personal-copilot-instructions/copilot-readme/github.svg)](https://agentmods.dev/instructions/ismola/personal-copilot-instructions/copilot-readme)
Your own site
<a href="https://agentmods.dev/instructions/ismola/personal-copilot-instructions/copilot-readme"><img src="https://agentmods.dev/badge/instructions/ismola/personal-copilot-instructions/copilot-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.

agentmods 80×15 button for personal-copilot-instructions copilot-readme.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ismola/personal-copilot-instructions/copilot-readme"><img src="https://agentmods.dev/badge/instructions/ismola/personal-copilot-instructions/copilot-readme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 573 This file is loaded in full into every session.
When invoked 573 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00573 $0.00573
Opus 5.5 $0.00229 $0.00229
Sonnet 5.5 $0.00115 $0.00115
Haiku 4.5 $0.00057 $0.00057

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

Security

Grade A, and why

personal-copilot-instructions copilot-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/copilot-readme.instructions.md · 25 lines

What it actually says

Instrucciones para generación de README con Copilot

  • Antes de generar o actualizar el README, analiza obligatoriamente la estructura y los archivos reales del proyecto (incluyendo archivos y carpetas presentes en el sistema de archivos).
  • Solo incluye secciones en el README que correspondan a archivos o configuraciones realmente detectados en el proyecto. No generes secciones genéricas ni plantillas.
  • Si el archivo README ya existe, preserva y adapta el contenido existente al nuevo formato, nunca elimines información relevante.
  • El README debe comenzar con el nombre del proyecto y una breve descripción de su propósito.
  • Explica claramente qué hace el proyecto y su caso de uso principal.
  • Si el proyecto es grande y tiene una estructura algo compleja de archivos, incluye una sección de estructura del proyecto, detallando los directorios y archivos principales.
  • Solo añade una sección de variables de entorno requeridas si existen archivos .env, referencias a variables de entorno en el código (por ejemplo, process.env), o documentación relacionada en el proyecto. Si no existen, no incluyas ninguna sección de variables de entorno.
  • Si el proyecto necesita comandos para inciarse, como npm i, python install requirements o el comando similar al lenguaje del proyecto, incluye una sección de "Cómo iniciar el proyecto" con los pasos necesarios para la instalación y ejecución
  • Si existe un archivo .devcontainer, explica cómo usar el entorno de desarrollo remoto con VS Code. Si no existe, no incluyas ninguna sección sobre Devcontainer.
  • Si existe un archivo docker-compose.yml, explica cómo levantar el entorno con Docker Compose, incluyendo los comandos necesarios. Si no existe, no incluyas ninguna sección sobre Docker Compose.
  • Si el proyecto tiene un archivo package.json, documenta los comandos disponibles (scripts) y su función. Si no existe, no incluyas ninguna sección sobre scripts de package.json.
  • Si el proyecto es una API, genera un archivo adicional API_DOC.md que explique los endpoints, métodos, parámetros, respuestas y ejemplos de uso.
  • No incluyas secciones sobre Docker Compose, Devcontainer, scripts de package.json, variables de entorno, etc., si los archivos o referencias correspondientes no existen en el proyecto.
  • El README debe ser siempre una adaptación fiel al contexto y archivos presentes, evitando plantillas genéricas.
  • Si el proyecto tiene pruebas, explica cómo ejecutarlas.
  • Si el proyecto tiene integración continua o despliegue automatizado (como una github action), documenta el flujo básico solo si aplica.
  • Utiliza emojis y elementos visuales llamativos (tablas, listas, bloques destacados) para mejorar la legibilidad y hacer el README más atractivo.
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.

  1. 2mo ago First seen · 25 lines · 573 tokens per session scan A 7c3805015e97

Subscribe to this mod's changes

personal-copilot-instructions copilot-readme.instructions.md is an instructions file published in the GitHub repository Ismola/personal-copilot-instructions (1 stars, last pushed 1y ago), licensed MIT. It adds 573 tokens to every session, about $0.0023 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.

Writing and docscopilot
Related

personal-copilot-instructions copilot-readme.instructions.md compared with instructions from other repositories

personal-copilot-instructions copilot-readme.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
personal-copilot-instructions copilot-readme.instructions.mdIsmola/personal-copilot-instructionsInstructions file11y agoMITA573GitHub Copilot
plan-forge dapr.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA4,975GitHub Copilot
plan-forge database.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA1,890GitHub Copilot
plan-forge naming.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA1,453GitHub Copilot
plan-forge caching.instructions.mdsrnichols/plan-forgeInstructions file62d agoMITA733GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode