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 2233admin/design-pipeline --skill publish-project-to-githubgit clone --depth 1 https://github.com/2233admin/design-pipelineWrote 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/2233admin/design-pipeline/publish-project-to-github)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/publish-project-to-github"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/publish-project-to-github.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.1 | $0.00090 | $0.01802 |
| Opus 5 | $0.00045 | $0.00901 |
| Sonnet 5 | $0.00018 | $0.00360 |
| Haiku 4.5 | $0.00009 | $0.00180 |
Grade A, and why
publish-project-to-github 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 4d 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.
This is a copy
100% identical to publish-project-to-github — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Project to GitHub
Turn a finished local project into a clean public artifact. Treat repository creation, public visibility, and deployment as separate gates; a successful push is not proof that the public site works.
Deliverables
Produce the applicable items:
- a narrowly scoped Git repository
- an intentional public or private GitHub repository
- a project-specific
README.md - a real preview image when the project is visual
- a portable build or remix prompt when it adds value
- a configured GitHub Pages site for compatible web projects
- post-push and post-deploy read-back
1. Resolve scope and authority
Inspect the local project, repository state, remotes, and local instructions before writing.
Confirm or safely infer:
- the exact project directory and intended files
- repository name and owner
- whether the target should be public or private
- whether an existing repository must be updated or a new one created
- whether the user wants a live website, source hosting only, or both
Creating a public repository is authorized only when the user explicitly asks for public sharing, a public URL, open source, or equivalent. Otherwise ask for visibility before creating it.
Never force-push, overwrite an existing remote, change repository visibility, or replace an existing Pages configuration without exact authorization.
2. Audit before packaging
Run the bundled audit from the project root:
bash /path/to/publish-project-to-github/scripts/audit_public_project.sh .
Then inspect findings rather than treating the script as a substitute for judgment.
Block publication on:
- API keys, tokens, private keys, passwords, or
.envfiles - personal data or private client information
- absolute local filesystem paths required at runtime
- unlicensed or private assets
- missing runtime files
- unclear ownership of a repository name that already exists
Review all external runtime URLs and generated assets. State any required network dependency in the README.
What ships with it
4 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.
- 4d ago First seen · 229 lines · 90 tokens per session scan A e41c4372cc0b
publish-project-to-github is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 1,802 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to publish-project-to-github, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
release-retrospective
Produce a structured look-back after a major release or deprecation — capturing what the plan got right, what it missed, and what to do differently. Trigger when someone says: release retrospective, post-release review, what went wrong with the release, how did the deprecation go, release post-mortem, retro on the…
version-bump-advisor
Recommend the correct semver bump with reasoning and a generated changelog entry. Trigger when someone says: what version bump, is this a breaking change, semver recommendation, should this be major or minor, version this release, changelog entry, what kind of release is this, or anything about versioning a design…
design-tokens-versioning
Semantic versioning for design tokens — deprecation, breaking changes, and migration. Use this when releasing token changes or planning a major bump.
cs-ending-time
Use when the user asks to finish, ship, publish, commit, push, or deploy a completed implementation in one bounded delivery scope.
git-publish-release
A release assistant for GitHub, a service for hosting software projects. It compares project history and creates a GitHub Release with notes for a chosen version tag.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…