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 skills add ulises-jeremias/agent-toolkit --skill assistantgit 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/skills/ulises-jeremias/agent-toolkit/assistant)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/assistant"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/assistant.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.1 | $0.00064 | $0.03440 |
| Opus 5 | $0.00032 | $0.01720 |
| Sonnet 5 | $0.00013 | $0.00688 |
| Haiku 4.5 | $0.00006 | $0.00344 |
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 6d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assistant
Organizational companion for anyone building **for ** in any repository (client, internal, or ``). It tells the agent what to open first, why, and how to resolve conflicts—without copying content that already lives in the project.
Orchestration
This skill is the default orchestrator and fallback for agent work. Read references/ORCHESTRATION.md for routing (workflows, tool skills, delegation phrasing). Use ~/.local/share//skills/skill-catalog.yaml (bundled next to skills) for domain, WHAT vs HOW, triggers, and depends_on per skill. Workflow skills define phases and gates only; tool skills own CLI procedures—do not inline HOW steps inside workflow skills.
Hard rules
- Derive answers from files in the repo and **machine-local agent-toolkit baseline (
~/.local/share/agent-toolkit/). Cite paths when you recommend workflows. - Do not paraphrase long sections of README/docs into chat when a link or path is enough; do not invent scripts or flags that are not documented or discoverable.
- AGENTS.md (when present) is the primary contract for agent behavior in that repo; see Agent instruction map for tie-breakers with tool-specific files.
Extended path hints: references/REPO_INSPECTION.md. Orchestration: references/ORCHESTRATION.md. Starter AGENTS.md for new projects: references/AGENTS_TEMPLATE.md (and chezmoi AGENTS.project.md.tmpl in the baseline templates).
Expected behavior
- On entering a task in a repo, spend a short discovery pass: follow Repository inspection order before editing large areas of code.
- Classify documentation you find (see Documentation taxonomy) so you do not apply contributor-only rules to end-user docs or vice versa.
- Prefer official automation from
Makefile/justfile/package.json/ CI over ad-hoc commands. - When advising, name the source file (“per
CONTRIBUTING.md…”, “.github/workflows/ci.ymlruns…”). - If something is missing (no tests doc, no AGENTS, conflicting instructions), say so and suggest a concrete addition—optionally offer to draft from
references/AGENTS_TEMPLATE.md. - Stay portable: avoid recommending workflows that only work in one IDE unless the repo is explicitly single-tool.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 223 lines · 64 tokens per session scan A dba1d6eae08a
assistant is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 3,440 once invoked, about $0.0003 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 skills, from other repositories
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
iblai-api-catalog-media
Manage an ibl.ai organization's catalog media resources via the Data Manager API — videos, images, documents, audio, and external links attached to a course, unit, or resource (item). Per-org, per-user CRUD plus search and by-item lookup, with multipart file upload. Use when attaching media to course/unit/resource…
iblai-api-agent-skill
Manage an ibl.ai agent's skills via the platform API — browse the org skill catalog, assign/unassign skills to an agent, and create/edit/delete catalog skills. Requires a connected sandbox. Use when giving an agent reusable skill instructions.
iblai-api-agent-safety
Configure an ibl.ai agent's moderation and safety systems via the platform API — enable flags, system prompts and responses (saved through the agent settings endpoint) — and review or delete flagged-prompt moderation logs. Use when setting guardrails or auditing flagged content.
iblai-api-agent-disclaimer
Manage an ibl.ai agent's disclaimers via the platform API — the Advisory text (saved through the agent settings endpoint) and the User Agreement (create/update/activate). Use when adding legal or advisory notices users must see or accept.
pr-alignment-loop
Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…