craft AGENTS.md

Development instructions for the Craft plugin, including its coding conventions and commands for building, checking, linting, and testing. They also explain how to run unit and integration tests.

In plain words
What is it for?
Use them when changing the Craft plugin, running its tests, checking documentation, validating counts, or building its documentation site.
Why use it?
They give a coding agent the repository-specific steps needed to make changes without skipping required checks.

Instructions file for CodexOpenCode

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/data-wise/craft/agents-md
Clone the repo
git clone --depth 1 https://github.com/Data-Wise/craft

Made for: Codex, OpenCode.

Per session 2,118 This file is loaded in full into every session.
When invoked 2,118 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.02118 $0.02118
Opus 5 $0.01059 $0.01059
Sonnet 5 $0.00424 $0.00424
Haiku 4.5 $0.00212 $0.00212

Measured yesterday against content hash 4bec3b23db92, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

craft 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 yesterday.

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 · 351 lines

How it starts

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

AGENTS.md - Development Guidelines for Craft Plugin

This document provides development guidelines for agentic coding assistants working on the Craft plugin repository. It covers build/lint/test commands, code style conventions, and project-specific practices.

Build/Lint/Test Commands

Primary Test Commands

# Run all unit tests (581+ tests, ~90% coverage)
python3 tests/test_craft_plugin.py

# Run all tests with pytest (includes integration tests)
python3 -m pytest tests/ -v

# Run specific test file
python3 tests/test_craft_plugin.py::TestClass::test_method

# Run integration tests only
python3 tests/test_integration_*.py

# Run dependency system tests
bash tests/test_dependency_management.sh

# Run specific integration test
python3 tests/test_integration_dependency_system.py

Linting and Validation

# Validate command/skill/agent counts match documentation
./scripts/validate-counts.sh

# Markdown linting (24 rules enforced)
npx markdownlint-cli2 "**/*.md" --config .markdownlint.json

# Build documentation site
mkdocs build

# Check broken links (with ignore rules)
python3 tests/test_craft_plugin.py -k "broken_links"

Development Workflow

# Quick validation (lint + test counts)
./scripts/validate-counts.sh && python3 tests/test_craft_plugin.py

# Full CI validation
python3 -m pytest tests/ -v && npx markdownlint-cli2 "**/*.md"

# Documentation validation
mkdocs build && python3 tests/test_craft_plugin.py -k "broken_links"

Code Style Guidelines

Python Conventions

Imports
# Standard library imports first
import json
import os
import re
from dataclasses import dataclass, field
from pathlib import Path
from typing import Dict, List, Optional, Tuple

# Third-party imports (none in this project)

# Local imports (alphabetized)
from .complexity_scorer import calculate_complexity_score
from .validators import validate_command_structure
Type Hints
  • Always use type hints for function parameters and return values
  • Use Optional[T] for nullable types, not Union[T, None]
  • Use List[T], Dict[K, V] instead of bare list, dict
  • Use dataclasses with field() for complex defaults

Read the full file on GitHub · 351 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. yesterday First seen · 351 lines · 2,118 tokens per session scan A 4bec3b23db92

Subscribe to this mod's changes

craft AGENTS.md is an instructions file published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 2,118 tokens to every session, about $0.0106 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-31.

Related

Other instructions, from other repositories