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/amitpatole/claude-genkit-plugin/agents-mdgit clone --depth 1 https://github.com/amitpatole/claude-genkit-pluginWrote 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/amitpatole/claude-genkit-plugin/agents-md)<a href="https://agentmods.dev/instructions/amitpatole/claude-genkit-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/amitpatole/claude-genkit-plugin/agents-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.1 | $0.02940 | $0.02940 |
| Opus 5 | $0.01470 | $0.01470 |
| Sonnet 5 | $0.00588 | $0.00588 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade A, and why
claude-genkit-plugin 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 5d 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Agents Documentation
This repository uses autonomous agents that run 24/7 to manage deployments, monitor health, and maintain the codebase.
Overview
Two primary agents operate continuously:
- Schedule Enforcement Agent - Ensures all deployments occur during the approved time window
- Monitoring & Maintenance Agent - Monitors health, fixes issues, and manages updates
Agent 1: Schedule Enforcement Agent
Purpose
Enforces strict deployment schedules to ensure all pushes, releases, and deployments occur only during the approved time window.
Schedule
- Runs: Every 5 minutes (24/7)
- Workflow:
.github/workflows/schedule-enforcement-agent.yml
Deployment Window
ALLOWED: 10:00 PM - 8:00 AM EST BLOCKED: 8:00 AM - 10:00 PM EST
Features
- ✅ Checks all deployment workflows for schedule compliance
- ✅ Blocks deployments outside the allowed window
- ✅ Monitors recent workflow runs for violations
- ✅ Generates violation reports
- ✅ Provides real-time status updates
- ✅ Heartbeat monitoring to confirm agent is running
Actions Taken
- Pre-deployment Check: Every deployment workflow first checks if current time is within the window
- Block on Violation: Exits with error code 1 if deployment attempted outside window
- Generate Reports: Creates violation reports in
agent-reports/directory - Status Updates: Updates
.github/agent-status/schedule-enforcement.txtevery 5 minutes
How It Works
# Check if within deployment window (10 PM - 8 AM EST)
CURRENT_HOUR=$(TZ='America/New_York' date +%H)
# Hours 22-23 (10 PM - 11:59 PM) OR 0-7 (12 AM - 7:59 AM) = ALLOWED
# Hours 8-21 (8 AM - 9:59 PM) = BLOCKED
if [ "$CURRENT_HOUR" -ge 22 ] || [ "$CURRENT_HOUR" -lt 8 ]; then
echo "✅ Within deployment window - Proceeding"
else
echo "🚫 BLOCKED: Outside deployment window"
exit 1
fi
Modified Workflows
All deployment workflows now include schedule enforcement:
publish-vscode-extension.ymlvscode-extension-ci.yml(publish job)vscode-extension-release.yml
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.
- 5d ago First seen · 426 lines · 2,940 tokens per session scan A e7bce61479d9
claude-genkit-plugin AGENTS.md is an instructions file published in the GitHub repository amitpatole/claude-genkit-plugin (11 stars, last pushed 5mo ago), licensed MIT. It adds 2,940 tokens to every session, about $0.0147 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
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.
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.
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).