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.
git clone --depth 1 https://github.com/OSideMedia/higgsfield-ai-prompt-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/commands/osidemedia/higgsfield-ai-prompt-skill/release)<a href="https://agentmods.dev/commands/osidemedia/higgsfield-ai-prompt-skill/release"><img src="https://agentmods.dev/badge/commands/osidemedia/higgsfield-ai-prompt-skill/release/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/commands/osidemedia/higgsfield-ai-prompt-skill/release"><img src="https://agentmods.dev/badge/commands/osidemedia/higgsfield-ai-prompt-skill/release.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.00014 | $0.00529 |
| Opus 5 | $0.00007 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
release 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 10d 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
Walk through a release for version $ARGUMENTS (e.g. /release 2.1.0).
If no version argument is provided, check CHANGELOG.md for the latest version and ask what the new version should be.
Steps:
- Sanitize the version argument — before using
$ARGUMENTSin any shell command, confirm it is a bare semantic version matching^[0-9]+\.[0-9]+\.[0-9]+$(e.g.2.1.0). If it contains anything else (spaces,;, backticks, quotes, path separators), STOP and ask the user for a clean version string — never interpolate an unvalidated argument into thegit commit/git tag/gh release createshell snippets below. - Release gate — run
python3 scripts/validate.py --strict,python3 -m pytest tests/ -q, andpython3 scripts/validate.py --evals. Stop if any of the three fails. - Changelog check — confirm CHANGELOG.md has an entry for this version. If not, ask what to add.
- Regenerate the user guide + manifest — AFTER the frontmatter version/date are bumped:
python3 scripts/generate_user_guide.py, thenpython3 scripts/validate_user_guide.py(manifest-fallback comparison; review any flagged drift), thenpython3 scripts/validate_user_guide.py --write-manifestand stage the refresheddocs/user-guide/MANIFEST.json. The PDF itself is a release artifact — it is git-ignored, never committed. - Commit — stage and commit any pending changes with message:
feat: v$ARGUMENTS — <summary from changelog> - Tag — create git tag
v$ARGUMENTS - Push — push commit and tag:
git push && git push --tags - GitHub release — create release from the tag:
gh release create v$ARGUMENTS --title "v$ARGUMENTS" --notes-file -using the changelog entry as notes. - Attach the guide —
gh release upload v$ARGUMENTS docs/user-guide/USER-GUIDE.pdfso the PDF ships with the release instead of the git history.
Confirm with the user before each destructive/visible step (commit, push, release).
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.
- 10d ago First seen · 22 lines · 14 tokens per session scan A b87df6c29a2a
release is a command published in the GitHub repository OSideMedia/higgsfield-ai-prompt-skill (522 stars, last pushed 18d ago), licensed MIT. It adds 14 tokens to every session and 529 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.