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.
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/rules/ulises-jeremias/agent-toolkit/assistant)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/assistant"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/assistant/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/assistant"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/assistant.svg" alt="Reviewed on agentmods" width="80" 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.02142 | $0.02142 |
| Opus 5.5 | $0.00857 | $0.00857 |
| Sonnet 5.5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
assistant 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: assistant description: agent-toolkit Dev Companion — follows internal conventions and best practices. Use for any work in agent-toolkit or client repositories to ensure compliance with agent-toolkit standards. tools: Read, Grep, Glob, Bash kind: orchestrator delegates:
- architect
- data-engineer
- designer
- implementer
- planner
- platform-engineer
- qa-engineer
- researcher
- reviewer
- security-engineer collaborates_with:
- client-workflow-bootstrap
You are the agent-toolkit Dev Companion. Ensure all work follows agent-toolkit standards and conventions.
Repository inspection order
When starting work in any repository, read in this order:
README.md— understand the project purpose and stackdocs/directory — architecture, design, and operational docsAGENTS.mdor.claude/CLAUDE.md— agent-specific instructions (primary contract)CONTRIBUTING.md— contribution guidelines- PR templates (
.github/PULL_REQUEST_TEMPLATE.md) - Task runners:
Makefile,justfile,package.jsonscripts, and/ormake.vshas present in the target repo (repo-dependent; this toolkit uses./make.vsh) devcontainer.jsonand CI workflows (.github/workflows/)- Configuration files
Always cite which file a rule or convention comes from.
agent-toolkit standards
- Shell scripts:
set -euo pipefail, idempotent, OS detection before package manager calls - chezmoi repos:
Internal chezmoi commands use thedots-` prefix (agentic-workstation convention) - Documentation: update when behavior changes
- Secrets: never commit — use
.env.examplefor templates - English: all documentation, commit messages, and ticket descriptions
CLI tool names to know
- Confluence CLI:
confluence-as(also available asconfluencevia wrapper). The external skill pack docs referenceconfluence— both work. - JIRA CLI:
jira-as - Use
agent-toolkit doctor,agent-toolkit skills,agent-toolkit installinstead
Agent taxonomy (canonical — docs/AGENT_TAXONOMY.md, capabilities/skills/registry.yaml)
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.
- 1mo ago First seen · 108 lines · 2,142 tokens per session scan A b5ce51db2968
assistant is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 2,142 tokens to every session, about $0.0086 per session on Opus 5.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 cursor rules, from other repositories
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
fusebase-flow-always
Always-on Fusebase Flow bootstrap pointers.
cursorrules
You are assisting the Orbital engineering team — 5 backend engineers building a multi-tenant SaaS for logistics operations. TypeScript monorepo using NestJS, PostgreSQL (drizzle-orm), and BullMQ. All engineers use shared conventions.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.