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-sop-writernpx skills add hoavdc/CodexKit --skill codexkit-sop-writergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-sop-writer)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-sop-writer"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-sop-writer.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 | $0.00039 | $0.00769 |
| Opus 5 | $0.00019 | $0.00385 |
| Sonnet 5 | $0.00008 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
codexkit-sop-writer 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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOP Writer
When to Use
- Documenting a recurring office, operations, finance, HR, support, or admin process.
- Turning tribal knowledge into repeatable instructions.
- Creating a first SOP draft for review by a process owner.
- Standardizing handoffs, approvals, evidence capture, or exception handling.
Procedure
Step 1 - Define Scope
State process purpose, start trigger, end state, included work, excluded work, and target users.
Step 2 - Identify Roles
List process owner, performers, approvers, reviewers, and escalation contacts.
Step 3 - Write Procedure
Use numbered steps. Each step should include:
- action
- owner
- input
- system or document used
- expected output
Step 4 - Add Controls And Exceptions
Document approval gates, quality checks, evidence retained, common exceptions, and escalation rules.
Step 5 - Add Maintenance
Set review cadence, version owner, and change log expectations.
Inputs
| Input | Required | Format |
|---|---|---|
| Process name and goal | Yes | Plain language |
| Process trigger and end state | Recommended | Event, deadline, output |
| Roles involved | Recommended | Owner, performer, approver |
| Current steps | Recommended | Notes, bullets, transcript |
| Controls or policies | Optional | Approval rules, compliance needs |
Output
# SOP - [Process Name]
## Purpose
## Scope
## Roles And Responsibilities
## Inputs And Systems
## Procedure
## Quality Checks
## Exceptions And Escalation
## Records / Evidence
## Review Cadence
## Changelog
Quality Criteria
- A new team member can follow the SOP without relying on tribal knowledge.
- Each step has an owner and expected output.
- Exceptions and escalation paths are clear.
- Controls and evidence requirements are included where relevant.
- The SOP avoids policy overclaims and is marked for process-owner review.
Verification (4C)
| Check | Question |
|---|---|
| Correctness | Does the SOP match the actual process and tool reality? |
| Completeness | Are scope, roles, steps, controls, exceptions, evidence, and maintenance covered? |
| Context-fit | Is the level of detail appropriate for process risk and frequency? |
| Consequence | What could break if someone followed this SOP exactly? |
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.
- yesterday First seen · 112 lines · 39 tokens per session scan A ae6f42297e28
codexkit-sop-writer is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 769 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
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
product-reviews
Help users design and facilitate product reviews that shift from status updates to strategic deep-dives, ensuring high-quality craftsmanship and organizational alignment.
delivering-delegated-linear-issues
当用户明确要求领取、处理、批量清空或定时扫描 Linear 的 Delegated to Agent issue 时使用；按队列状态、领取竞争、交付路径和收尾四个阶段渐进读取。.
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.