sign-tools: Instructions file for GitHub Copilot

.github/copilot-instructions.md

sign-tools copilot-instructions.md is an instructions file for GitHub Copilot from sign-protocol/sign-tools. It costs 549 tokens per session, scanned A, original, Apache-2.0.

A set of development rules for a monorepo supporting the SIGN-LANG project. A monorepo keeps several related tools and shared code in one repository, and SIGN-LANG is the project’s open-source language ecosystem.

In plain words
What is it for?
Use it when changing a tool under packages, shared utilities, specifications, plans, policies, documentation, or other parts of the SIGN-LANG repository.
Why use it?
It gives agents a clear workflow for choosing the right tool specification, policy, plan, and approval level before editing. It also sets boundaries between shared code and individual tools.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: mentions AGENTS.md; mentions Codex.

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

Reuse

Borrowing it

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

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 sign-tools copilot-instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sign-protocol/sign-tools/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sign-protocol/sign-tools/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 549 This file is loaded in full into every session.
When invoked 549 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.00549 $0.00549
Opus 5.5 $0.00220 $0.00220
Sonnet 5.5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

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

Security

Grade A, and why

sign-tools 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 1mo 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 · 62 lines

What it actually says

GitHub Copilot Instructions for Sign Tools

This is a monorepo for tools supporting the SIGN-LANG open-source project. As Copilot/Codex, adhere to these guidelines:

Repository Purpose

  • Mission: Provide reference implementations for SIGN-LANG ecosystem
  • Structure: Monorepo with packages/<tool>/ for each tool
  • First Tool: sign-ingest (document → SIGN converter)
  • Shared Code: shared/ for cross-tool utilities

Engineering Posture

  • Be truthful and explicit
  • Create durable artifacts
  • Prioritize maintainability
  • Use clear boundaries and small steps

Development Workflow

  1. Review request, constraints, and risk level
  2. Consult .agent/operating-system/product/README.md for repo intent
  3. For tool-specific work, read packages/<tool>/SPEC.md first
  4. For significant work, create/update plans in .agent/operating-system/plans/
  5. Seek approval for high-risk actions
  6. Implement incrementally with verification
  7. Keep docs synchronized with code changes

Standards and Policies

  • Follow .agent/policies/agent-coding-standards.md
  • Review approval boundaries: .agent/policies/approvals.md
  • Consider risk tiers: .agent/policies/risk-tiers.md

Approval Requirements

Request human approval for:

  • Irreversible data changes
  • Security/auth modifications
  • Production infrastructure changes
  • New public integrations
  • Security weakening changes

Documentation Updates

Documentation is part of the product. Update when system truth changes:

  • Tool-specific changes: packages/<tool>/ docs
  • Shared changes: shared/, docs/, repo README
  • Decisions: .agent/operating-system/decisions/

Repository Structure

sign-tools/
├── .agent/               # Agentic OS (policies, plans, decisions)
├── packages/
│   └── sign-ingest/     # First tool
├── shared/              # Shared utilities
├── docs/                # Shared documentation
└── AGENTS.md, README.md, CONTRIBUTING.md

For Adding a New Tool

  1. Create packages/<tool-name>/ with README and SPEC.md
  2. Follow existing tool patterns
  3. Update root README.md with tool description
  4. Create implementation plan if substantial
  5. Ensure code passes repo standards c:\CareerHighways\sign-tools.github\copilot-instructions.md
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. 1mo ago First seen · 62 lines · 549 tokens per session scan A b08095ba6bea

Subscribe to this mod's changes

sign-tools copilot-instructions.md is an instructions file published in the GitHub repository sign-protocol/sign-tools (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 549 tokens to every session, about $0.0022 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.

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,649 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,549 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,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens