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/nayjest/ai-microcore/agents-mdgit clone --depth 1 https://github.com/Nayjest/ai-microcoreWrote 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/nayjest/ai-microcore/agents-md)<a href="https://agentmods.dev/instructions/nayjest/ai-microcore/agents-md"><img src="https://agentmods.dev/badge/instructions/nayjest/ai-microcore/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.01454 | $0.01454 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
ai-microcore 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI coding agents (Claude Code, Codex, etc.) when working with code in this repository.
Overview
AI MicroCore (ai-microcore, importable as microcore) is a thin adapter layer over LLM
providers and vector/semantic-search databases. The whole point is provider-agnosticism:
application code calls llm(...), tpl(...), texts.search(...) and the concrete backend
(OpenAI, Anthropic, Google, a CLI tool, a local Transformers model, an arbitrary Python
function, ChromaDB, Qdrant, ...) is selected purely by configuration. When changing behavior,
preserve this property — adding a parameter or branch that forces application code to know which
backend is active works against the core design.
Commands
Tests run locally with pytest (no Docker required); the Makefile targets wrap the same
commands in a Docker container (make test, make cs, make black) and are mainly for the
maintainer's workflow.
pip install -r requirements/dev.txt # test + lint + build tooling
pytest # runs tests/basic (the default testpath, no network)
pytest tests/basic/test_llm.py # single file
pytest tests/basic/test_llm.py::test_name # single test
pytest tests/apis # hits REAL API services; needs .env.test.* + keys
flake8 microcore tests examples # max-line-length=100 (.flake8)
pylint microcore # config in .pylintrc
black microcore tests examples # formatter; commits are expected to be black-clean
python -m microcore test-llm <.env-file> [<prompt>] # smoke-test a provider config live
Note pyproject.toml sets testpaths = ["tests/basic"] and asyncio_mode = "auto", so a bare
pytest only runs the basic suite. Other suites: tests/extended, tests/cache, tests/local
(Transformers), tests/apis (live). CI (.github/workflows/tests.yml) runs the basic suite on
Python 3.10–3.13 and pylint separately.
Architecture
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 · 93 lines · 1,454 tokens per session scan A 65c2f9c5a0a2
ai-microcore AGENTS.md is an instructions file published in the GitHub repository Nayjest/ai-microcore (108 stars, last pushed 8d ago), licensed MIT. It adds 1,454 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
repomix base.instructions.md
Instructions for yamadashy/repomix: Please make sure to check the rules written in .agents/rules/base.md as they contain important project-specific guidelines and instructions.
repomix copilot-instructions.md
Copilot instructions for yamadashy/repomix, a project described as: 📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file. Perfect for when you need to feed your codebase to Large Language Models (LLMs) or other AI tools like Claude, ChatGPT, DeepSeek, Perplexity, Gemini…
langgraphjs CLAUDE.md
Claude Code instructions for langchain-ai/langgraphjs, covering langgraphjs development guide, corridor security analysis, build & test commands, code style guidelines and library architecture.
langgraphjs AGENTS.md
AGENTS.md instructions for langchain-ai/langgraphjs, covering repository instructions and corridor security analysis.
redis-vl-python CLAUDE.md
Claude Code instructions for redis/redis-vl-python, covering claude.md - redisvl project context, frequently used commands, development workflow, redis setup and documentation.
attackgen AGENTS.md
AGENTS.md instructions for mrwadams/attackgen, covering agents.md, project overview, development commands, running the application and installing dependencies.