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 dev-companiongit 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/dev-companion)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/dev-companion"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/dev-companion/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/skills/ulises-jeremias/agent-toolkit/dev-companion"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/dev-companion.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.00034 | $0.01066 |
| Opus 5 | $0.00017 | $0.00533 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
dev-companion 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 7d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Companion (WHAT) — general layer (L2)
This skill is the general dev companion for work. It does not replace assistant (orchestrator); it sits above workflows and names what to invoke next.
Language: English for ticket comments, PR text, and user-facing outputs when this companion drives delivery work.
Layering
| Layer | Skill | Role |
|---|---|---|
| L1 | assistant | Repo inspection order, conflict resolution, fallback |
| L2 (this skill) | dev-companion | Companion framing: modes, gates, delegation for client work |
| L3 | Workspace pack overlay | Client/account-specific context loaded from ~/.ai-workspace/packs/ |
If engagement triggers match, load the appropriate workspace pack overlay first, then proceed with workflow-generic-project. Do not mix multiple workflow drivers on the same task.
Mode selection
- Default for /client delivery: use workflow-generic-project for phased delivery.
- If the user mentions an engagement, ticket prefix, or repo context → load the matching pack from the workspace (overlay) and apply its boundaries/gates.
- If unclear → ask before applying L3.
Delegation (HOW is in other skills)
| Need | Delegate to |
|---|---|
| Discovery, AGENTS conflict handling | assistant |
| Generic client delivery phases | workflow-generic-project |
| Planning / default workflow / validation | planning / development-workflow |
| Work items, incidents, meetings, decisions, agreements, spikes | work-item, incident, meeting-minutes, decision-log, agreement, spike |
| Project assessments, evidence maps, technical/management unit scorecards | project-assessment, project-assessment-evidence, technical-unit-assessment, management-unit-assessment |
| ClickUp | clickup-cli |
| Jira | External jira-* pack (jira-assistant router; CLI: jira-as) |
| Confluence | External confluence-* pack (confluence-assistant router; CLI: confluence-as or confluence) |
| Draft PR GitHub / GitLab | github-cli-workflow / gitlab-cli-workflow (for default body when the repo has no template: pr-fallback first) |
| CI failures (GitHub Actions) | gh-fix-ci |
| Merge / rebase conflicts | fix-merge-conflicts |
| Prose quality before PR | unslop |
| Code slop in diff | deslop |
| Large change scope | blast-radius |
| Session learnings | workspace-knowledge-sync |
| Where to save deliverables + human review | output-handshake |
| UI depth | figma / figma-implement-design |
| Workstation health | triage |
What ships with it
1 file 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.
- 7d ago First seen · 72 lines · 34 tokens per session scan A cb145011d670
dev-companion is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,066 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
meeting-transcript
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering.
lark-workflow-standup-report
A workflow that combines calendar events with unfinished Lark tasks to produce a daily or weekly work summary.
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
outlook-calendar
A skill for managing Microsoft Outlook and Microsoft 365 calendar events through a connected account.
iblai-api-agent-support
Manage an ibl.ai agent's human-support tickets via the platform API — list and filter the tickets users raised with an agent (by agent, requester, status, session), read a ticket's conversation thread, reply as the support team, change ticket status, and close or delete tickets. Use when triaging or responding to…
Automate Lark and Feishu docs, sheets, mail, calendar, meetings, and chat tasks from agents with Lark CLI
Operate Lark and Feishu work objects from one agent-ready CLI instead of stitching together separate APIs and browser flows.