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/yellowback/forgejo-claude-code-action/claude-mdgit clone --depth 1 https://github.com/yellowback/forgejo-claude-code-actionWrote 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.
[](https://agentmods.dev/instructions/yellowback/forgejo-claude-code-action/claude-md)<a href="https://agentmods.dev/instructions/yellowback/forgejo-claude-code-action/claude-md"><img src="https://agentmods.dev/badge/instructions/yellowback/forgejo-claude-code-action/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00497 | $0.00497 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
forgejo-claude-code-action 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 3d 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 — 59 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 when working with code in this repository.
Development Tools
- Runtime: Bun 1.2.11
Common Development Tasks
Available npm/bun scripts from package.json:
# Test
bun test
# Formatting
bun run format # Format code with prettier
bun run format:check # Check code formatting
Architecture Overview
This is a GitHub Action that enables Claude to interact with GitHub PRs and issues. The action:
- Trigger Detection: Uses
check-trigger.tsto determine if Claude should respond based on comment/issue content - Context Gathering: Fetches GitHub data (PRs, issues, comments) via
github-data-fetcher.tsand formats it usinggithub-data-formatter.ts - AI Integration: Supports multiple Claude providers (Anthropic API, AWS Bedrock, Google Vertex AI)
- Prompt Creation: Generates context-rich prompts using
create-prompt.ts - MCP Server Integration: Installs and configures GitHub MCP server for extended functionality
Key Components
- Trigger System: Responds to
/claudecomments or issue assignments - Authentication: OIDC-based token exchange for secure GitHub interactions
- Cloud Integration: Supports direct Anthropic API, AWS Bedrock, and Google Vertex AI
- GitHub Operations: Creates branches, posts comments, and manages PRs/issues
Project Structure
src/
├── check-trigger.ts # Determines if Claude should respond
├── create-prompt.ts # Generates contextual prompts
├── github-data-fetcher.ts # Retrieves GitHub data
├── github-data-formatter.ts # Formats GitHub data for prompts
├── install-mcp-server.ts # Sets up GitHub MCP server
├── update-comment-with-link.ts # Updates comments with job links
└── types/
└── github.ts # TypeScript types for GitHub data
Important Notes
- Actions are triggered by
@claudecomments or issue assignment unless a different trigger_phrase is specified - The action creates branches for issues and pushes to PR branches directly
- All actions create OIDC tokens for secure authentication
- Progress is tracked through dynamic comment updates with checkboxes
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.
- 3d ago First seen · 59 lines · 497 tokens per session scan A 14c0e9e1f2a3
forgejo-claude-code-action CLAUDE.md is an instructions file published in the GitHub repository yellowback/forgejo-claude-code-action (5 stars, last pushed 1y ago), licensed MIT. It adds 497 tokens to every session, about $0.0025 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.
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).
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.
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.
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.
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).
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.