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 agentmods add skills/hoavdc/codexkit/codexkit-hiring-ops-coordinatornpx skills add hoavdc/CodexKit --skill codexkit-hiring-ops-coordinatorgit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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 | $0.00057 | $0.00582 |
| Opus 5 | $0.00028 | $0.00291 |
| Sonnet 5 | $0.00011 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
codexkit-hiring-ops-coordinator 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hiring Ops Coordinator
Purpose
Convert recruiting activity into one operating view with candidate movement and follow-ups.
When to use
- interview feedback is stale or fragmented
- recruiters need a clean next-step queue
- hiring managers want a weekly funnel summary
When not to use
- the user needs talent strategy or final candidate evaluation
- the content includes sensitive HR issues beyond scheduling and flow
Inputs
- candidate stages and dates
- interview feedback status
- scheduling constraints
- next-step decisions if known
Procedure
- Map each candidate to stage, owner, and next step.
- Flag missing feedback and stale stages.
- Separate scheduling blockers from decision blockers.
- Collapse the list into a short funnel summary plus action queue.
- Provide a recruiter-ready follow-up block if useful.
Output
- candidate movement summary
- stale feedback or scheduling gaps
- next actions by owner
Definition of done
- recruiters can see where flow is blocked
- every active candidate has a current owner and next step
- the output is suitable for a weekly hiring ops check-in
Examples
- "Summarize this hiring funnel and flag missing interviewer feedback."
- "Turn these recruiting notes into actions for recruiter and hiring manager."
Quality Criteria
- Steps are executable in sequence without external context
- Decision points have clear if/then branching
- Rollback or abort procedures are documented for risky steps
- Expected duration or time-per-step is estimated
Verification (4C)
| Check | Question |
|---|---|
| Correctness | Do the steps execute correctly in the order specified? |
| Completeness | Are decision points, error handling, and escalation paths all documented? |
| Context-fit | Could someone with the right access but no prior context complete this runbook? |
| Consequence | If Step N fails and the operator skips to Step N+1, what breaks? |
Edge Cases
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.
- 2d ago First seen · 82 lines · 57 tokens per session scan A c0c50f3e734b
codexkit-hiring-ops-coordinator is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 582 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
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
agent-planner
Agent skill for planner - invoke with $agent-planner.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
maintain
Maintain the slopus/happy open source project. Triage issues, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…