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/izkreny/agentifico/agents-mdgit clone --depth 1 https://github.com/izkreny/agentificoWrote 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/izkreny/agentifico/agents-md)<a href="https://agentmods.dev/instructions/izkreny/agentifico/agents-md"><img src="https://agentmods.dev/badge/instructions/izkreny/agentifico/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 | $0.00990 | $0.00990 |
| Opus 5 | $0.00495 | $0.00495 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
agentifico 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 4d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentifico
AI agent skills, instructions and gotchas, published two ways: a Claude Code plugin marketplace, and skills that install on their own.
This file is for any agent working in this repository, whatever its harness, and it is deliberately minimal: it holds only what no other file already owns. Conventions that come from the gh-solo plugin, or from the agent's own instructions, are not restated here.
Layout
| Path | What it holds |
|---|---|
.claude-plugin/marketplace.json |
the marketplace manifest, one entry per plugin |
plugins/<name>/ |
one plugin, with its own manifest, skills, agents and hooks |
skills/<name>/ |
a skill that ships on its own, outside any plugin |
docs/plans/ |
one implementation plan per branch |
scripts/ |
this repository's own checks, and their benches |
.agents/gh-solo.md |
the per-repository facts the gh-solo plugin reads |
AGENTS.md, CLAUDE.md |
this file; the second is a symlink to the first |
Each plugin, and each skill under skills/, is a package
A package is released on its own tag, <name>_<version>, and carries its own version inside it - a plugin in plugins/gh-solo/.claude-plugin/plugin.json and its marketplace entry, a skill in its frontmatter under metadata.version.
A change to one package is not a change to another, and no package's version moves for another's change. That is the rule the tag scheme exists to make true, and it is what makes skills/ and plugins/ peers rather than a hierarchy: a skill under plugins/gh-solo/skills/ ships when the plugin does, a skill under skills/ ships when it alone is tagged.
A change to a package's own files moves that package's version, on the branch that makes the change. Which part moves follows from what the change does to whoever installs the package: a breaking change moves the major, new behaviour the minor, and everything else the patch, with a ! or a BREAKING CHANGE: trailer on the commit marking the first. The commit type is a hint at that and never the rule, since a feat can break an interface and a chore can leave one alone. Every path outside a plugins/<name>/ or skills/<name>/ directory is repository-level, owns no version and moves none, so a change confined to such paths leaves every version where it was.
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.
- 4d ago First seen · 42 lines · 990 tokens per session scan A a413466aaed3
agentifico AGENTS.md is an instructions file published in the GitHub repository izkreny/agentifico (2 stars, last pushed 4d ago), licensed MIT. It adds 990 tokens to every session, about $0.0049 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.