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 Azzygoatcoder/agent-useful-skills --skill dev-workflowgit clone --depth 1 https://github.com/Azzygoatcoder/agent-useful-skillsWrote 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/azzygoatcoder/agent-useful-skills/dev-workflow)<a href="https://agentmods.dev/skills/azzygoatcoder/agent-useful-skills/dev-workflow"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/dev-workflow/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/azzygoatcoder/agent-useful-skills/dev-workflow"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/dev-workflow.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.00131 | $0.02172 |
| Opus 5.5 | $0.00052 | $0.00869 |
| Sonnet 5.5 | $0.00026 | $0.00434 |
| Haiku 4.5 | $0.00013 | $0.00217 |
Grade A, and why
dev-workflow 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 23d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Workflow — GitHub 协作与发布
issue → PR → review → merge → release 是一条链。本技能用一个入口覆盖全链，先判场景再走对应流程。
原先拆成 issue-skill / pr-skill / review-skill / release-skill 四个同级技能，它们共享同一套 remote 约定与 push 权限判据，互相引用，还各自占一条 catalog——2026-09-12 合并。
第 0 步：共用判据（所有场景先做）
先统一 remote 命名，再谈角色。 origin 本身不携带含义——git 把「你 clone 的那个仓库」
叫 origin，所以它可能是权威仓库，也可能是你的 fork。
| remote | 含义 |
|---|---|
origin |
你 clone 的那份（可能=权威仓库，也可能=你的 fork） |
upstream |
权威仓库（仅当它与 origin 不同时存在） |
判定用权限，不用 remote 名字：
gh api repos/{owner}/{repo} --jq .permissions.push # true = 有直推权限
| push 权限 | 角色 | issue | PR | release |
|---|---|---|---|---|
| true | Owner / Maintainer | 分诊/关闭 | 直推即可，想要评审才开 PR | 场景 A 直推 |
| false | Contributor | 只能提 | fork-PR 是唯一路径 | 场景 B fork-PR |
若「只 clone 了自己的 fork」而没有 upstream，先补上：
git remote add upstream https://github.com/<权威owner>/<repo>.git
⚠️ 写操作（push /
gh release/gh pr/gh issue）一律显式指名 remote 或--repo， 不要依赖gh的自动推断——多 remote 时它可能挑错目标。
默认分支统一这样取（git rev-parse --abbrev-ref HEAD 返回的是当前分支，不能用）：
gh repo view <owner>/<repo> --json defaultBranchRef -q .defaultBranchRef.name
场景判定
| 场景 | 触发 | 详细流程 |
|---|---|---|
| A. issue — 提 / 分诊 / 关闭 / 转 PR | "报 bug"、"提 feature"、"看 issue"、"分诊"、"关 issue"、"修这个 issue" | references/issue.md |
| B. PR — 开 PR、推分支到 fork | "提 PR"、"开 PR"、"submit PR"、"做完一批改动想合入" | references/pr.md |
| C. review — 看 / 评审 / 合并 PR | "review 这个 PR"、"看下这个 PR"、"approve"、"要求修改"、"merge"、"合了" | references/review.md |
| D. release — bump / tag / 发 Release | "release"、"发版本"、"发 rc"、"准备发 vX.Y.Z" | references/release.md |
⚠️ 走 D 之前先确认「Release 由谁创建」：仓库若有 tag 触发的 release workflow， 只推 tag、不要手跑
gh release create—— 两者抢跑不会报错，而是让 CI 的创建步骤跳过、 连带把产物上传也跳过，最终留下一个 有 notes 但没有产物的 Release。 判断方法与恢复步骤见 references/release.md 的「发布机制」一节。
What ships with it
5 files 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.
- 23d ago Changed · +6 lines 3e1f8a8e61bb
- 1mo ago First seen · 86 lines · 131 tokens per session scan A 0982c88a4fb5
dev-workflow is a skill published in the GitHub repository Azzygoatcoder/agent-useful-skills (9 stars, last pushed 22d ago), licensed MIT. It adds 131 tokens to every session and 2,172 once invoked, about $0.0005 per session on Opus 5.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-13.
Other skills, from other repositories
dsh-changelog
A release-note writing guide for maintaining a CHANGELOG, a file that records what changed in each software version. It follows Keep a Changelog categories and semantic versioning rules.
dsh-plugin-publish
A publishing procedure for putting a DSH plugin on GitHub and adding it to the DSH community list. DSH is the plugin ecosystem described by the procedure, and GitHub is the code-hosting service where the plugin is published.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
comet-archive
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.
skillshare-release
Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new…
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…