markdy-com: Instructions file for GitHub Copilot

.github/copilot-instructions.md

markdy-com copilot-instructions.md is an instructions file for GitHub Copilot from HoangYell/markdy-com. It costs 426 tokens per session, scanned A, original, MIT.

Repository instructions for an open-source tool that lets developers create animated architecture diagrams from code.

In plain words
What is it for?
They are for guiding development and release work on a diagram-as-code project, including running checks, updating release notes, publishing packages, and creating GitHub releases.
Why use it?
They give the coding agent the project's rules for testing, releasing, publishing packages, and handling requests such as shipping a release.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is HoangYell/markdy-com's own configuration. It tells GitHub Copilot how to work on markdy-com 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 markdy-com configures →

Reuse

Borrowing it

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

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 markdy-com copilot-instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hoangyell/markdy-com/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/hoangyell/markdy-com/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 426 This file is loaded in full into every session.
When invoked 426 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.00426 $0.00426
Opus 5.5 $0.00170 $0.00170
Sonnet 5.5 $0.00085 $0.00085
Haiku 4.5 $0.00043 $0.00043

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

Security

Grade A, and why

markdy-com copilot-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/copilot-instructions.md · 18 lines

What it actually says

Copilot instructions for this repository

  • When the user says ship it, release it, or gives shorthand like commit, PR, merge, release, tag it, interpret that as a request to run the full shipping workflow for the current completed changes.
  • The default shipping workflow for this repo is:
    1. validate the current change with the full CI suite: pnpm run ci (runs unit tests, AST backward compatibility gates, documentation examples, and Chrome DevTools headless E2E verification)
    2. commit the finished product changes with a repo-style commit message
    3. open a PR and wait for checks
    4. merge the PR once checks pass
    5. cut the next patch release with pnpm run release <next-version>
    6. ensure CHANGELOG.md contains concrete release notes before the release commit is created
    7. push the version tag and confirm the GitHub Release workflow succeeds
  • Prefer the existing release automation in scripts/release.sh instead of manually stitching together a release flow.
  • All 8 packages are dual-published:
    • npmjs.com: Distributed under @markdy/* (e.g. @markdy/core, @markdy/renderer-dom, @markdy/mcp-server)
    • GitHub Packages: Distributed under @hoangyell/* on https://npm.pkg.github.com via scripts/publish-packages.mjs
  • CI runs 4 parallelized jobs (quality, test matrix across Node 20 & 22, devtools-e2e, and website). The quality job runs pnpm run build prior to pnpm run typecheck to ensure emitted declarations are available for cross-package workspace imports.
  • Keep the homepage example picker curated. Favor the strongest showcase scenes and avoid cluttering the homepage with weak, repetitive, or overly diagnostic examples.
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 · 18 lines · 426 tokens per session scan A fd9842f0afbd

Subscribe to this mod's changes

markdy-com copilot-instructions.md is an instructions file published in the GitHub repository HoangYell/markdy-com (104 stars, last pushed 12d ago), licensed MIT. It adds 426 tokens to every session, about $0.0017 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-30.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens