agentmods.dev

wordpress-claude-stack copilot-instructions.md

A project instruction file for a WordPress site using PHP, Gutenberg, ACF, and WooCommerce.

In plain words
What is it for?
Use it when building WordPress themes, blocks, REST endpoints, custom fields, or shop features in that project.
Why use it?
It sets coding and security rules for handling data, forms, database queries, permissions, and output safely.

Instructions file for GitHub Copilot

3 4mo ago A scan 278 tokens original MIT
View the source file mvtandas/wordpress-claude-stack
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/mvtandas/wordpress-claude-stack/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/mvtandas/wordpress-claude-stack

Made for: GitHub Copilot.

Per session 278 This file is loaded in full into every session.
When invoked 278 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.00278 $0.00278
Opus 5 $0.00139 $0.00139
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

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

Security

Grade A, and why

wordpress-claude-stack 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 · 29 lines

What it actually says

Copilot Instructions — WordPress Project

Framework

  • WordPress 6.x with PHP 8.2+ (strict types)
  • Follow WordPress Coding Standards (WPCS)
  • Gutenberg for blocks, ACF for custom fields
  • WooCommerce for e-commerce features

Generate code that:

  • Uses declare(strict_types=1) at top of PHP files
  • Escapes all output: esc_html(), esc_attr(), esc_url()
  • Sanitizes all input: sanitize_text_field(), absint()
  • Uses $wpdb->prepare() for ALL database queries
  • Verifies nonces: wp_verify_nonce()
  • Checks capabilities: current_user_can()
  • Uses WP_Query for queries, never query_posts()
  • Prefixes all functions/hooks with project namespace
  • Uses WordPress APIs: get_option(), get_post_meta(), get_transient()
  • Registers REST routes with register_rest_route() and permission callbacks

Never generate:

  • Raw SQL without $wpdb->prepare()
  • Unescaped output
  • query_posts() calls
  • extract() or eval()
  • Hardcoded URLs (use home_url(), admin_url())
  • Short PHP tags <?
  • Code without nonce verification on forms
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 · 29 lines · 278 tokens per session scan A 01abc3c9d06c

Subscribe to this mod's changes

wordpress-claude-stack copilot-instructions.md is an instructions file published in the GitHub repository mvtandas/wordpress-claude-stack (3 stars, last pushed 4mo ago), licensed MIT. It adds 278 tokens to every session, about $0.0014 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.

acfaiclaude-codecopilotcursorcursorrules
Related

Other instructions, from other repositories

memorix GEMINI.md

Instructions for AVIDS2/memorix, covering memorix - cross-agent memory rules, session start - bind project, then load context, during session - capture important context, architecture & decisions and bug fixes & problem solving.

AVIDS2/memorix · 846 tokens

Ctxo CLAUDE.md

Instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).

alperhankendi/Ctxo · 5,885 tokens

awesome-reviewers CLAUDE.md

Instructions for baz-scm/awesome-reviewers, covering awesome reviewers — repository guidelines, what this project is, source of truth, site layer and machine interface.

baz-scm/awesome-reviewers · 1,008 tokens

llm-ide-rules AGENTS.md

Instructions for iloveitaly/llm-ide-rules, covering code comments, important workflow rules, alembic migrations, default content for new non-nullable columns and 1. add the column as nullable (no default needed).

iloveitaly/llm-ide-rules · 6,061 tokens

llm-ide-rules pytest-integration-tests.instructions.md

Instructions for iloveitaly/llm-ide-rules, covering pytest integration tests and example integration test.

iloveitaly/llm-ide-rules · 1,299 tokens

llm-ide-rules pytest-tests.instructions.md

Instructions for iloveitaly/llm-ide-rules, covering pytest tests, example test and file structure.

iloveitaly/llm-ide-rules · 561 tokens