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 athola/claude-night-market --skill development-workflowgit clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/athola/claude-night-market/development-workflow)<a href="https://agentmods.dev/skills/athola/claude-night-market/development-workflow"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/development-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/athola/claude-night-market/development-workflow"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/development-workflow.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.00020 | $0.01227 |
| Opus 5 | $0.00010 | $0.00613 |
| Sonnet 5 | $0.00004 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
development-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 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Table of Contents
- Overview
- Available Modules
- Quick Start
- Usage Patterns
- For New Projects
- For Existing Projects
- For Team Onboarding
- Integration Benefits
- Quality Assurance
- Customization
- Support and Resources
Development Workflow Hub
This modular skill provides a detailed framework for software development workflows. It's designed as a hub that coordinates specialized modules for different aspects of development.
Overview
Get started quickly with this development workflow framework:
** Quick Start**: Set up repository structure and basic workflow in minutes
- Initialize with git-workflow module
- Add code-review process for team collaboration
- Implement testing strategies for quality assurance
Progressive Learning: Start simple, add complexity as needed
- Basic workflow → git-workflow and code-review
- Quality focus → add testing-strategies and documentation
- Production ready → add deployment-procedures and monitoring
** Use Case-Based**: Jump directly to what you need
- New project? → Start with git-workflow
- Team scaling? → Focus on code-review + testing
- Production deployment? → Use deployment-procedures
- Documentation debt? → Apply documentation-guidelines
Available Modules
This workflow illustrates a hub coordinating these specialized
modules. Each link below resolves to a working example file in
this skill's modules/ directory; copy the directory and adapt
the contents when using this template for a real skill:
- modules/git-workflow.md: Repository setup, branching strategies, and daily git practices
- modules/code-review.md: Pull request process, review guidelines, and quality standards
- modules/testing-strategies.md: Unit testing, integration testing, and E2E testing patterns
- modules/documentation-guidelines.md: Code documentation, API docs, and README standards
- modules/deployment-procedures.md: CI/CD pipelines, environment setup, and monitoring
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.
- 9d ago First seen · 164 lines · 20 tokens per session scan A fea0c595dc81
development-workflow is a skill published in the GitHub repository athola/claude-night-market (336 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 1,227 once invoked, about $0.0001 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
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
ship
Use when changes are ready to ship — takes the working tree to a pull request with code review, Conventional Commit, automatic SemVer bump and a PR template. Part of the cys flow (after cys:check).
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…