assistant

assistant is a cursor rule for Cursor from ulises-jeremias/agent-toolkit. It costs 2,142 tokens per session, scanned A, original, MIT.

An orchestration rule for work in agent-toolkit and client repositories. It sets the inspection order and routes tasks to specialists such as architects, implementers, testers, reviewers, and security engineers.

In plain words
What is it for?
Use it when starting development or maintenance work in a repository, especially when the project has agent-toolkit standards and several specialist roles.
Why use it?
It gives repository work a consistent starting point by checking project instructions, documentation, contribution rules, task scripts, and CI configuration. It also helps choose the right specialist instead of handling every task the same way.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Good fit Use it when starting development or maintenance work in a repository, especially when the project has agent-toolkit standards and several specialist roles.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ulises-jeremias/agent-toolkit/assistant
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

Made for: Cursor.

Wrote 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.

agentmods badge for assistant

README.md
[![agentmods](https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/assistant/github.svg)](https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/assistant)
Your own site
<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.

agentmods 80×15 button for assistant

Your own site · 80×15
<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>
Per session 2,142 This file is loaded in full into every session.
When invoked 2,142 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash b5ce51db2968, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugins/agent-toolkit-agents/rules/assistant.mdc · 108 lines

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:

  1. README.md — understand the project purpose and stack
  2. docs/ directory — architecture, design, and operational docs
  3. AGENTS.md or .claude/CLAUDE.md — agent-specific instructions (primary contract)
  4. CONTRIBUTING.md — contribution guidelines
  5. PR templates (.github/PULL_REQUEST_TEMPLATE.md)
  6. Task runners: Makefile, justfile, package.json scripts, and/or make.vsh as present in the target repo (repo-dependent; this toolkit uses ./make.vsh)
  7. devcontainer.json and CI workflows (.github/workflows/)
  8. 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 the dots-` prefix (agentic-workstation convention)
  • Documentation: update when behavior changes
  • Secrets: never commit — use .env.example for templates
  • English: all documentation, commit messages, and ticket descriptions

CLI tool names to know

  • Confluence CLI: confluence-as (also available as confluence via wrapper). The external skill pack docs reference confluence — both work.
  • JIRA CLI: jira-as
  • Use agent-toolkit doctor, agent-toolkit skills, agent-toolkit install instead

Agent taxonomy (canonical — docs/AGENT_TAXONOMY.md, capabilities/skills/registry.yaml)

Read the full file on GitHub · 108 lines

Changes

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.

  1. 1mo ago First seen · 108 lines · 2,142 tokens per session scan A b5ce51db2968

Subscribe to this mod's changes

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.

Related

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…

katalon-labs/true-skills · 195 tokens

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…

katalon-labs/true-skills · 131 tokens

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…

katalon-labs/true-skills · 126 tokens

fusebase-flow-always

Always-on Fusebase Flow bootstrap pointers.

fusebase-dev/fusebase-flow · 163 tokens

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.

caioribeiroclw-pixel/pluribus · 829 tokens

fusebase-flow-implementation

Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.

fusebase-dev/fusebase-flow · 0 tokens