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 openteams-lab/openteams --skill ashby-automationgit clone --depth 1 https://github.com/openteams-lab/openteamsWrote 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/openteams-lab/openteams/ashby-automation)<a href="https://agentmods.dev/skills/openteams-lab/openteams/ashby-automation"><img src="https://agentmods.dev/badge/skills/openteams-lab/openteams/ashby-automation/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/openteams-lab/openteams/ashby-automation"><img src="https://agentmods.dev/badge/skills/openteams-lab/openteams/ashby-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.01637 |
| Opus 5 | $0.00015 | $0.00818 |
| Sonnet 5 | $0.00006 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
Ashby Automation 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 9d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- Ashby Automation — 100% identical, 0 lines differ
- ashby-automation — 100% identical, 2 lines differ
- Ashby Automation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ashby Automation
Automate your Ashby ATS recruiting operations directly from Claude Code. Create candidates, post jobs, manage applications, view interview schedules, and search your talent pipeline -- all without leaving your terminal.
Toolkit docs: composio.dev/toolkits/ashby
Setup
- Add the Rube MCP server to your Claude Code config with URL:
https://rube.app/mcp - When prompted, authenticate your Ashby account through the connection link provided
- Start automating your recruiting workflows with natural language
Core Workflows
1. Manage Candidates
Create, list, search, update, and retrieve detailed candidate information.
Tools: ASHBY_CREATE_CANDIDATE, ASHBY_LIST_CANDIDATES, ASHBY_SEARCH_CANDIDATES, ASHBY_GET_CANDIDATE_INFO, ASHBY_UPDATE_CANDIDATE
Create a candidate named "Jane Smith" with email [email protected] and LinkedIn profile https://linkedin.com/in/janesmith
Key parameters for ASHBY_CREATE_CANDIDATE:
name(required) -- full name of the candidateemail-- primary email addressphoneNumber,linkedInUrl,githubUrl,websiteUrl-- contact/social profiles
Key parameters for ASHBY_SEARCH_CANDIDATES:
email-- exact email matchname-- partial name match
Key parameters for ASHBY_LIST_CANDIDATES:
perPage(max 100) /cursor-- paginationsyncToken-- for incremental updates since last sync
2. Create and List Jobs
Post new job openings and browse existing positions.
Tools: ASHBY_CREATE_JOB, ASHBY_LIST_JOBS, ASHBY_GET_JOB_INFO
Create a new "Senior Software Engineer" job in team dept-123 at location loc-456 with brand brand-789
Key parameters for ASHBY_CREATE_JOB:
title(required) -- job titleteamId(required) -- department/team ID (from list departments)locationId(required) -- office location ID (from list locations)brandId(required) -- employer brand ID (from list brands)defaultInterviewPlanId-- required to open the job for applicationsjobTemplateId-- pre-populate from a template
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.
- 9d ago First seen · 168 lines · 30 tokens per session scan A c22112e41fc6
Ashby Automation is a skill published in the GitHub repository openteams-lab/openteams (612 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 1,637 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-03.
Other skills, from other repositories
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…
pipeline-conductor
Use when a pipeline conductor session is being seeded, or when inspecting/debugging one. Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, preflight every candidate to one deterministic claim verdict, stand up one worker…
babysit
Use when the user says "babysit", "monitor", "keep checking", "keep an eye on", "loop on this PR", "let me know when", or wants polling that outlives a wait+poll window. Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop…