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.
npx agentmods add instructions/friendsofhyperf/components/claude-mdgit clone --depth 1 https://github.com/friendsofhyperf/componentsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01466 | $0.01466 |
| Opus 5 | $0.00733 | $0.00733 |
| Sonnet 5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
components CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Overview
This is a monorepo containing 50+ production-ready components for the Hyperf PHP framework. Each component in src/ is independently installable and can be split into its own repository.
- PHP Version: >=8.2
- Framework: Hyperf >=3.2.0
- Testing Framework: Pest (PHPUnit under the hood)
- License: MIT
Development Commands
Testing
# Run all tests (lint, unit, type coverage)
composer test
# Run unit tests only
composer test:unit
# Or directly: vendor/bin/pest
# Run specific test group
vendor/bin/pest --group=telescope
vendor/bin/pest --group=http-client
# Run linting (code style check)
composer test:lint
# Run type coverage analysis
composer test:types
Code Quality
# Fix code style issues
composer cs-fix
# Run static analysis (PHPStan)
composer analyse
# Run type coverage analysis
composer analyse:types
Component Management
# Normalize composer.json files across all components
composer json-fix
# Generate README.md for components
composer gen:readme
# Check for pending repository changes
composer repo:pending
Architecture
Monorepo Structure
Each component follows a standardized structure:
src/{component-name}/
├── composer.json # Component-specific dependencies
├── LICENSE
├── README.md
└── src/
├── ConfigProvider.php # Hyperf auto-discovery
└── [component files]
Configuration Providers
All components use Hyperf's ConfigProvider pattern for auto-discovery. When a component is installed, Hyperf automatically registers it via the ConfigProvider class. Key patterns:
- Namespace Convention:
FriendsOfHyperf\{ComponentName} - ConfigProvider defines: dependencies, commands, listeners, aspects, annotations
- Publishing: Components can publish config files and migrations to user applications
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.
- 2d ago First seen · 233 lines · 1,466 tokens per session scan A 1d47a15c9995
components CLAUDE.md is an instructions file published in the GitHub repository friendsofhyperf/components (115 stars, last pushed 11d ago), licensed MIT. It adds 1,466 tokens to every session, about $0.0073 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.
Other instructions, from other repositories
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.