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 cass-2003/local-workflow-skill --skill software-engineeringgit clone --depth 1 https://github.com/cass-2003/local-workflow-skillWrote 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/cass-2003/local-workflow-skill/software-engineering)<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/software-engineering"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/software-engineering/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/cass-2003/local-workflow-skill/software-engineering"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/software-engineering.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.00103 | $0.00917 |
| Opus 5 | $0.00051 | $0.00458 |
| Sonnet 5 | $0.00021 | $0.00183 |
| Haiku 4.5 | $0.00010 | $0.00092 |
Grade A, and why
software-engineering 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.
What it actually says
coff0xc-software-engineering
快速规则（日常任务先读这里）
[先读仓库] 先看 AGENTS/README、package/lockfile、入口、测试脚本和当前 dirty worktree。 [最小修复] 只改请求范围；先复现/定位，再小步 patch，不做无关重构和新框架迁移。 [验证闭环] 先跑目标 test/typecheck/lint/build，再按风险加宽；没跑不能写已验证。 [Git 边界] 不回滚用户改动；push、PR、删除、生产、凭据、CI/CD 权限先确认。
普通开发任务按本节直接执行；只有大功能、架构/API/schema/auth、CI 发布或 skill 质量验证才展开完整工作流。
如果任务升级为多文件、多阶段、多 skill、架构/API/schema/auth 或多 worker 工作，先让 coff0xc-skill-router 读取 references/complex-workflow.md。本 skill 在该流程中负责实现、repo repair、测试和 diff 卫生。
能力定位
面向真实仓库的工程交付能力。适合把模糊需求变成可运行代码、可复现修复、可验证测试结果和清晰 diff 摘要。
能交付什么
- 代码补丁、脚本或配置修改
- 失败原因和根因链路说明
- 单元/集成/构建验证结果
- Git diff 摘要和剩余风险
可以接收什么输入
- 本地仓库、报错日志、测试输出、issue 描述
- 需求草稿、接口说明、UI 截图或现有模块
- package/lockfile、README、AGENTS、CI 脚本
放心使用的边界
- 可直接做本地、可逆、低风险的代码和测试改动
- 删除、远程 push、生产配置、凭据、付费服务和 CI/CD 权限变更必须先确认
- 不为小问题引入新框架或无必要依赖
- 默认只处理本地、可逆、可验证的低风险工作；涉及生产、凭据、付费、远程写入、删除、发布或权限变更时必须先确认。
为什么可以放心
- 先读项目结构和现有风格，再修改
- 先跑窄验证，再按风险跑宽验证
- 未运行的测试不会写成已通过
典型使用方式
使用 coff0xc-software-engineering 修复这个 repo 的 failing tests，并说明验证结果。
使用 coff0xc-software-engineering 少问确认，直接实现这个多文件开发任务。
Use coff0xc-software-engineering to build this admin panel feature end to end with tests.
默认输出
- 收口只写完成、验证、还剩、下一步；有文件/代码/规则产物给路径或位置。
- 未真实运行的检查标为未验证，安全/架构结论标证据等级。
按需展开
- 日常任务只执行上面的快速规则、能力边界和典型用法，不默认读取完整门禁。
- 深度架构、复杂多阶段、质量评测、发版、正式交付或当前任务证据不足时，再读取
references/full-workflow.md。 - 读取 reference 后仍保持最小必要上下文；不要因为 reference 存在就输出长篇流程或额外自证材料。
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.
- 6d ago First seen · 60 lines · 103 tokens per session scan A f41e882e0df9
software-engineering is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 2mo ago), licensed MIT. It adds 103 tokens to every session and 917 once invoked, about $0.0005 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
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.