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 psylch/better-skills --skill better-skill-publishgit clone --depth 1 https://github.com/psylch/better-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/psylch/better-skills/better-skill-publish)<a href="https://agentmods.dev/skills/psylch/better-skills/better-skill-publish"><img src="https://agentmods.dev/badge/skills/psylch/better-skills/better-skill-publish/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/psylch/better-skills/better-skill-publish"><img src="https://agentmods.dev/badge/skills/psylch/better-skills/better-skill-publish.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.00104 | $0.01241 |
| Opus 5 | $0.00052 | $0.00620 |
| Sonnet 5 | $0.00021 | $0.00248 |
| Haiku 4.5 | $0.00010 | $0.00124 |
Grade A, and why
better-skill-publish 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 11d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Publish
Language
Match user's language: Respond in the same language the user uses.
Overview
Package a agent skill into a complete, distributable GitHub repository. Generates all the surrounding files (README, LICENSE, plugin.json, marketplace.json) and optionally creates the GitHub repo.
How It Works
- Identify the skill to publish
- Optionally review first with better-skill-review
- Collect publishing metadata through dialogue
- Generate the repository structure with
publish.py - Optionally initialize git and create GitHub repo
Dialogue Flow
Progress:
- Step 1: Identify the skill
- Step 2: Pre-publish validation
- Step 3: Collect metadata
- Step 4: Generate repository
- Step 5: Post-generation
Step 1: Identify the Skill
Accept the skill location in multiple forms:
| Input | Detection | Action |
|---|---|---|
| Directory with SKILL.md | Direct path | Use as-is |
| SKILL.md file path | Path ends in SKILL.md |
Use parent directory |
| Current directory | No input, cwd has SKILL.md | Auto-detect |
Step 2: Pre-Publish Validation
Check for better-skill-review availability:
- First try:
{SKILL_DIR}/../better-skill-review/scripts/validate.py - Fallback:
~/.agents/skills/better-skill-review/scripts/validate.py
If found, suggest running validation:
python3 <validate.py path> run --path <skill-path>
If there are failures, recommend fixing them before proceeding. Warnings are acceptable.
If better-skill-review is not available, offer:
- A) Install it:
npx skills add psylch/better-skills@better-skill-review -g -y - B) Continue without it (quick manual check: verify SKILL.md exists with valid frontmatter)
- C) Cancel
Step 3: Collect Metadata
Use AskUserQuestion to gather:
-
GitHub owner/org — Default: try to infer from
git config user.nameorgh api user -q .login. Ask user to confirm or change. -
Repository name — Default:
<skill-name>-skill(e.g.,cors-audit-skill). Suggest the convention but let user override.
What ships with it
10 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.
- references/distribution_guide.md 2.5 KB
- scripts/publish.py 9.3 KB runs code
- templates/gitignore.tmpl 74 B
- templates/LICENSE_apache2.tmpl 742 B
- templates/LICENSE_gpl3.tmpl 753 B
- templates/LICENSE_mit.tmpl 1.0 KB
- templates/marketplace.json.tmpl 240 B
- templates/plugin.json.tmpl 232 B
- templates/README.md.tmpl 565 B
- templates/README.zh.md.tmpl 502 B
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.
- 11d ago First seen · 170 lines · 104 tokens per session scan A c6d2f9e3f5a5
better-skill-publish is a skill published in the GitHub repository psylch/better-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 104 tokens to every session and 1,241 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-08-31.
Other skills, from other repositories
clawhub-production-release
Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.
dev-workflow
The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.
pr-submission
PR title format, commit conventions, and pre-PR checklist for SkillHub. Use when preparing or reviewing pull requests.
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
devops/changelog-generation
A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.
odoo-commit
Guides Odoo-style commit creation following official Odoo git guidelines. Drafts [TAG] module: short description messages, checks whether to amend or create a new commit, stages files explicitly, commits via git commit -F, and keeps local history clean before PRs. Auto-invokes for commit-related requests in Odoo…