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 agentmods add commands/joshuaramirez/advanced-prompting-engine/releasegit clone --depth 1 https://github.com/JoshuaRamirez/advanced-prompting-engineWrote 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/joshuaramirez/advanced-prompting-engine/release)<a href="https://agentmods.dev/commands/joshuaramirez/advanced-prompting-engine/release"><img src="https://agentmods.dev/badge/commands/joshuaramirez/advanced-prompting-engine/release.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.00000 | $0.00633 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00063 |
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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Create a GitHub release for the advanced-prompting-engine package. Run /pre-release first.
Arguments
$ARGUMENTS— optional: version (e.g., "0.5.0"). If omitted, reads current version from pyproject.toml.
Steps
1. Pre-flight
- If
$ARGUMENTSis provided, use it as the version. Otherwise read frompyproject.toml. - Verify git working tree is clean (excluding untracked files)
- Run
python3 -m pytest tests/ -q— any failure is a blocker - Verify CHANGELOG.md has a
## [x.y.z]section AND a[x.y.z]:comparison link for this version
If any check fails, STOP and report.
2. Version Bump (only if $ARGUMENTS provided and differs from current)
- Update version in
pyproject.toml - Update
__version__insrc/advanced_prompting_engine/__init__.py - Update
versionin.claude-plugin/plugin.json(marketplace manifest) - If CHANGELOG.md has no section for this version, generate one from
git log --oneline v{previous}..HEAD - Add comparison link:
[x.y.z]: https://github.com/JoshuaRamirez/advanced-prompting-engine/compare/v{previous}...v{new} - Commit:
git commit -am "v{version}: <brief summary>"
3. Push
git push origin main
4. Tag
git tag -a "v{version}" -m "Release v{version}"
git push origin "v{version}"
5. Create GitHub Release
Extract the CHANGELOG section between ## [x.y.z] and the next ## [ header. Save to a temp file. Then:
gh release create "v{version}" --title "v{version}" --notes-file /tmp/release_notes.txt --latest
6. Verify
gh release view "v{version}" --json tagName,url,createdAt
Report: version, tag, release URL, commit hash.
7. Post-release
- PyPI: the
publish.ymlworkflow triggers on release creation — publishes via OIDC trusted publisher automatically - Plugin marketplace: the
.claude-plugin/plugin.jsonversion was updated in step 2 and pushed in step 3 — the marketplace picks up the new version from the repo - Remind:
pip install -e ".[dev]"to update local install
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.
- 5d ago First seen · 59 lines · 0 tokens per session scan A 85ce6698c3a6
release is a command published in the GitHub repository JoshuaRamirez/advanced-prompting-engine (0 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 633 tokens. 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 commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
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.