dataJAR-recipes copilot-instructions.md

dataJAR-recipes copilot-instructions.md is an instructions file for GitHub Copilot from autopkg/dataJAR-recipes. It costs 2,045 tokens per session, scanned A, original, Apache-2.0.

Instructions for a set of Python linters that check and fix AutoPkg recipes. AutoPkg recipes are XML property files or YAML files that automate packaging software for macOS.

In plain words
What is it for?
Use them when adding, running, or maintaining recipe linters, the shared command-line runner, or checks that detect and repair packaging-file problems.
Why use it?
They standardize how each linter is structured and ensure the scripts run with AutoPkg's required Python environment and libraries.

Instructions file for GitHub Copilot

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/autopkg/datajar-recipes/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/autopkg/dataJAR-recipes

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 dataJAR-recipes copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/autopkg/datajar-recipes/copilot-instructions.svg)](https://agentmods.dev/instructions/autopkg/datajar-recipes/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/autopkg/datajar-recipes/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/autopkg/datajar-recipes/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,045 This file is loaded in full into every session.
When invoked 2,045 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.02045 $0.02045
Opus 5 $0.01022 $0.01022
Sonnet 5 $0.00409 $0.00409
Haiku 4.5 $0.00204 $0.00204

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

Security

Grade A, and why

dataJAR-recipes 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 5d 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.

*AutoPkg Linters/.github/copilot-instructions.md · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AutoPkg Recipe Linter Suite - AI Coding Agent Instructions

Project Overview

This is a suite of Python linters for validating and fixing AutoPkg recipes. AutoPkg recipes are XML plist or YAML files that automate software packaging for macOS. Each linter is a standalone script in its own directory that detects and fixes specific issues in recipe files.

Architecture: Unified CLI runner (autopkg-linter.py) + 16 independent linter modules, each following the same pattern.

Critical Environment Requirement

⚠️ All scripts MUST run using AutoPkg's Python: /usr/local/autopkg/python

Every script includes verify_environment() that checks sys.executable.startswith('/usr/local/autopkg'). This is not optional - AutoPkg recipes require AutoPkg's Python environment with its specific dependencies (plistlib, etc.).

Linter Architecture Pattern

Each linter follows this structure:

LinterName/
├── LinterName.py          # Main script with main() function
├── README.md              # Detailed documentation
└── __pycache__/          # Python bytecode cache

Standard Linter Structure

Every linter script contains:

  1. Shebang: #!/usr/local/autopkg/python
  2. verify_environment(): Validates Python path
  3. clean_path(): Handles drag-and-drop paths with escaped spaces
  4. process_plist_recipe(): Logic for XML plist recipes
  5. process_yaml_recipe(): Logic for YAML recipes (if applicable)
  6. main(): Interactive prompt for recipe directory, then scans/processes files

Recipe Format Handling

  • Plist recipes (.recipe): XML plist format using plistlib
  • YAML recipes (.yaml): YAML format using yaml module
  • Most linters support both formats with separate processing functions
  • Some operations (e.g., XML escaping) only apply to plist format

Suite Runner Integration

autopkg-linter.py dynamically loads and runs linters:

  1. get_available_linters(): Returns list of (number, name, directory, script, description) tuples
  2. load_linter_module(): Uses importlib.util.spec_from_file_location() to load scripts
  3. run_linter(): Temporarily overrides sys.argv and __builtins__.input to inject recipe directory and auto-answer prompts in bulk mode
  4. Modes:
    • bulk: Auto-provides recipe directory + default answers to all prompts
    • interactive: Provides recipe directory, then allows user interaction

Read the full file on GitHub · 214 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.

  1. 5d ago First seen · 214 lines · 2,045 tokens per session scan A f1121e9c5f93

Subscribe to this mod's changes

dataJAR-recipes copilot-instructions.md is an instructions file published in the GitHub repository autopkg/dataJAR-recipes (130 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,045 tokens to every session, about $0.0102 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.

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 · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js 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,296 tokens