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 agents/evalstate/fast-agent/pluginsgit clone --depth 1 https://github.com/evalstate/fast-agentWhat 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.00000 | $0.02604 |
| Opus 5 | $0.00000 | $0.01302 |
| Sonnet 5 | $0.00000 | $0.00521 |
| Haiku 4.5 | $0.00000 | $0.00260 |
Grade A, and why
plugins 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 yesterday.
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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugins
Plugins package reusable slash commands such as /find, /peek, or
/edit-last, post-user-turn displays, or both. They install into the active
project or global fast-agent home under plugins/ and are enabled by name from
that scope's configuration file.
plugins:
enabled:
- agent-finder
- edit-assistant
Install a plugin from the configured plugin registry:
fast-agent plugins add agent-finder
From an interactive fast-agent session, /plugins add makes the scope
explicit. If you omit it, fast-agent prompts with global as the default:
/plugins add agent-finder
/plugins add agent-finder --global
/plugins add agent-finder --project
Global plugins are available across projects. Project plugins are available only in the active project and override global plugins with the same name. Plugin listings use one combined project-then-global index. Update commands use the same indices and can be filtered without renumbering:
/plugins update all --global --yes
/plugins update 4 --global
/plugins update all --project --yes
Manage installed plugins:
fast-agent plugins list
fast-agent plugins update
fast-agent plugins update all --yes
fast-agent plugins remove agent-finder
fast-agent plugins list shows each installed plugin, the slash commands it
adds, and any configured key bindings from the plugin manifest.
Use --registry to point at a local or remote marketplace:
fast-agent plugins --registry ./marketplace.json add agent-finder
Plugin registries are used for direct plugin installs and updates. Card-pack dependencies use the card-pack registry that supplied the selected pack; see Card Packs for the coupling rule.
Global Plugins
Global plugin installs write to FAST_AGENT_HOME when it is set; otherwise
they use ~/.fast-agent. The plugin is enabled in that directory's
fast-agent.yaml:
FAST_AGENT_HOME=~/.fast-agent fast-agent plugins add agent-finder --global
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.
- yesterday First seen · 372 lines · 0 tokens per session scan A 93f282625acb
plugins is an agent published in the GitHub repository evalstate/fast-agent (3,904 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,604 tokens. 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 agents, from other repositories
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.
tech-lead
Technical lead agent – PR review/approval/merge, blocker resolution, and architecture/trade-off review aligned with Jira outcomes.
unittest-generator
Use this agent when you need to create unit tests for your code in unittest.TestCase format, organized in a tests folder with concept-based subfolders. Examples: Context: User has just written a new authentication module and needs comprehensive unit tests. user: 'I just finished writing my user authentication…
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
DocScribe
Write docs/ prose for a completed change, in caveman style, per the repo's Documentation Update Protocol. Use after a change lands to update docs/architecture.md, docs/ .md, README, or docs/AGENTS.md — the Rule-6 delegation target (main agent must NOT edit docs/ directly). Self-contained — give it the diff + target…