agentmods.dev

skill-provenance: Instructions file for Codex

AGENTS.md

skill-provenance AGENTS.md is an instructions file for Codex, OpenCode from snapsynapse/skill-provenance. It costs 1,167 tokens per session, scanned A, original, MIT.

Project instructions for Skill Provenance, a package that records the files, versions, and checksums of an AI-agent skill. A checksum is a fingerprint used to detect file changes.

In plain words
What is it for?
Use them when changing the skill bundle, updating its manifest or history, running verification, or creating its distribution packages.
Why use it?
They help agents verify that a skill bundle is intact and package or validate changes correctly.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md; mentions Codex; built for openclaw.

This is snapsynapse/skill-provenance's own configuration. It tells Codex and OpenCode how to work on skill-provenance 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 skill-provenance configures →

not rated 7repo changed 27d ago A scan 1,167 tokens original MIT
View source ↗ snapsynapse/skill-provenance skillprovenance.dev
Reuse

Borrowing it

Nothing to install: this file belongs to snapsynapse/skill-provenance. 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/snapsynapse/skill-provenance/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/snapsynapse/skill-provenance

Made for: Codex, OpenCode.

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 skill-provenance AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/snapsynapse/skill-provenance/agents-md/github.svg)](https://agentmods.dev/instructions/snapsynapse/skill-provenance/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/snapsynapse/skill-provenance/agents-md"><img src="https://agentmods.dev/badge/instructions/snapsynapse/skill-provenance/agents-md/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 skill-provenance AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/snapsynapse/skill-provenance/agents-md"><img src="https://agentmods.dev/badge/instructions/snapsynapse/skill-provenance/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,167 This file is loaded in full into every session.
When invoked 1,167 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.01167 $0.01167
Opus 5.5 $0.00467 $0.00467
Sonnet 5.5 $0.00233 $0.00233
Haiku 4.5 $0.00117 $0.00117

Measured 27d ago against content hash 000fb6eb8ad9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skill-provenance AGENTS.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 27d 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.

AGENTS.md · 99 lines

How it starts

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

Agents Guide

Instructions for AI agents (Claude, Codex, Gemini CLI, etc.) working on this repository. This metaskill is also published to ClawHub for discovery by OpenClaw agents.

Repository structure

skill-provenance/                ← Canonical source bundle (DO NOT rename)
├── SKILL.md                     ← Agent-facing skill definition
├── README.md                    ← Human-facing user guide (has internal version header)
├── MANIFEST.yaml                ← File inventory: roles, versions, SHA-256 hashes
├── CHANGELOG.md                 ← Recent in-bundle change history (last 5 entries)
├── evals.json                   ← 43 core evaluation scenarios
├── evals-distribution.json      ← 21 supplemental distribution evals
├── validate.sh                  ← Bash script for local hash verification
├── package.sh                   ← Bash script for derived strict/ClawHub outputs
└── references/standalone-verification.md ← No-plugin verify/bootstrap path
action.yml                       ← GitHub Actions Marketplace wrapper for validate.sh
verify.sh                        ← Standalone wrapper pinned to canonical validate.sh
CHANGELOG.md                     ← Full append-only repo history
skill-provenance.skill           ← Claude Settings ZIP (rebuilt from the directory)

The skill-provenance/ directory is the single source of truth. The .skill file is a packaging wrapper.

Before making changes

  1. Read skill-provenance/MANIFEST.yaml to understand the current bundle state.
  2. Run ./skill-provenance/validate.sh to confirm all hashes are clean.
  3. Read skill-provenance/CHANGELOG.md for recent context and root CHANGELOG.md if you need older release history.

After making changes

  1. Bump per-file version integers in MANIFEST.yaml for every file you changed.
  2. Recompute hashes: run ./skill-provenance/validate.sh --update.
  3. Bump bundle_version (semver) in MANIFEST.yaml:
    • PATCH for docs, typos, non-functional changes.
    • MINOR for new features, new files, capability additions.
    • MAJOR for breaking changes to the versioning model or spec.
  4. Update bundle_date to today.
  5. Add a new entry at the top of both changelogs:
    • skill-provenance/CHANGELOG.md keeps the newest 5 entries only.
    • CHANGELOG.md at repo root is the full append-only archive. Name every file that changed and describe what changed in each.
  6. Rebuild the .skill ZIP if bundle contents changed: 
    rm -f skill-provenance.skill
zip -r skill-provenance.skill skill-provenance/
  7. Run ./.github/scripts/release-surface-check.sh to confirm eval-count declarations, the standalone validator pin, GuideCheck sidecar metadata, and the .skill ZIP all match the current source.

Read the full file on GitHub · 99 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. 27d ago Changed · +2 lines · +47 tokens per session 000fb6eb8ad9
  2. 1mo ago Changed 5087711c69a1
  3. 1mo ago First seen · 97 lines · 1,120 tokens per session scan A e13120288b0d

Subscribe to this mod's changes

skill-provenance AGENTS.md is an instructions file published in the GitHub repository snapsynapse/skill-provenance (7 stars, last pushed 28d ago), licensed MIT. It adds 1,167 tokens to every session, about $0.0047 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.

LLMagentskillsai-agentsclaude-aideveloper-toolsgemini
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,384 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