agentmods.dev

tale copilot-instructions.md

The main coding instructions for the Tale repository, together with a separate file containing rules specific to that repository. They define how developers should reuse code, handle translations and data changes, meet accessibility standards, and verify results.

In plain words
What is it for?
They guide feature work, refactoring, database changes, translations, accessibility checks, testing, and verification of the actual application behavior.
Why use it?
They reduce inconsistent implementations by making repository-wide and project-specific rules part of every change.

Instructions file for GitHub Copilot

23 2d ago A scan 224 tokens original MIT
View the source file tale-project/tale
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/tale-project/tale/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/tale-project/tale

Made for: GitHub Copilot.

Per session 224 This file is loaded in full into every session.
When invoked 224 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00224 $0.00224
Opus 5 $0.00112 $0.00112
Sonnet 5 $0.00045 $0.00045
Haiku 4.5 $0.00022 $0.00022

Measured 2d ago against content hash 806042a7a1fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tale 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 2d 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

Tale — Copilot instructions

The canonical contract for working in this repository is AGENTS.md at the repo root — the shared tale-project contract — followed by .agents/repo.md, the repo-specific contract (layout, domain rules, skills index, debt ledger). Read both and follow them.

Non-negotiable reflexes (full rules in the two contracts):

  • Reuse before you write — search packages/ui, then shared app//lib/, then the feature; extend existing primitives, never fork them.
  • A change is rarely one file — translations in all base locales, docs with code, a migration for any data-model change, WCAG 2.1 AA for UI, and a test for every change.
  • Verify by observing the real outcome, not by inspection. Never claim a success you haven't seen.
  • Think before acting — classify the task, weigh impact, prefer the smallest correct, most reversible change.
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. 2d ago First seen · 18 lines · 224 tokens per session scan A 806042a7a1fe

Subscribe to this mod's changes

tale copilot-instructions.md is an instructions file published in the GitHub repository tale-project/tale (23 stars, last pushed 2d ago), licensed MIT. It adds 224 tokens to every session, about $0.0011 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-30.

Git and workflowLocalizationaiai-agentsautomationautomations
Related

Other instructions, from other repositories

baserow AGENTS.md

AGENTS.md instructions for baserow/baserow, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and localization.

baserow/baserow · 1,480 tokens

translate-book CLAUDE.md

Instructions for deusyu/translate-book, covering claude.md, project, structure, testing changes and then run translation via the skill.

deusyu/translate-book · 718 tokens

hana-developer-cli-tool-example translatable-text-handling.instructions.md

Use when adding user-facing text in CLI commands, API routes, or utilities. Enforces consistent use of bundle.getText() for all translatable strings, descriptive key naming, and multi-language synchronization across i18n/ property files.

SAP-samples/hana-developer-cli-tool-example · 2,470 tokens

tolgee-platform AGENTS.md

AGENTS.md instructions for tolgee/tolgee-platform, covering agents.md, repository structure, backend development, database migrations and backend testing.

tolgee/tolgee-platform · 2,094 tokens

xcstrings-crud CLAUDE.md

Instructions for Ryu0118/xcstrings-crud, covering xcstrings-crud, build & test, architecture, code style and key files.

Ryu0118/xcstrings-crud · 400 tokens

next-app-i18n-starter AGENTS.md

Instructions for s0vers/next-app-i18n-starter, covering agent guide, project, non-negotiables, cursor rules and deep reference.

s0vers/next-app-i18n-starter · 630 tokens