Borrowing it
Nothing to install: this file belongs to JoshuaRamirez/advanced-prompting-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JoshuaRamirez/advanced-prompting-engine/main/.claude/commands/pre-release.mdgit 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/pre-release)<a href="https://agentmods.dev/commands/joshuaramirez/advanced-prompting-engine/pre-release"><img src="https://agentmods.dev/badge/commands/joshuaramirez/advanced-prompting-engine/pre-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.00723 |
| Opus 5 | $0.00000 | $0.00362 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
pre-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 7d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Release Check
Run a comprehensive pre-release validation for the advanced-prompting-engine package. This checks everything needed before creating a GitHub release.
Steps
1. Version Consistency
Check that the version matches across all locations:
pyproject.toml→versionsrc/advanced_prompting_engine/__init__.py→__version__CHANGELOG.md→ has a section for this versionCHANGELOG.md→ has a comparison link for this version
Report any mismatches as blockers.
2. Test Suite
Run python3 -m pytest tests/ -v --tb=short and report the result. Any failure is a blocker.
3. Build Verification
Run python3 -m build to verify the package builds into a wheel and sdist. Report sizes. Any build failure is a blocker.
4. Import Chain
Run python3 -c "from advanced_prompting_engine.server import create_server; print('OK')" to verify the full import chain.
5. Content Audit
Check these files for stale references that don't match the current version:
README.md— node/edge counts, face/branch terminology, dimension count, grid sizes, doc referencesCLAUDE.md— same checkspyproject.tomldescription
Flag any stale content as a warning.
6. Git State
- Run
git status— working tree must be clean - Run
git log --oneline -5— show recent commits - Check if branch is ahead of origin (unpushed commits)
7. Dependency Check
- Verify no imports of deleted modules exist in any
.pyfile undersrc/ - Check for stale
__pycache__files for deleted modules
8. Integration Smoke Test
Run a quick end-to-end test:
import tempfile, os, networkx as nx
from advanced_prompting_engine.graph.canonical import build_canonical_graph
from advanced_prompting_engine.cache.embedding import EmbeddingCache
from advanced_prompting_engine.cache.tfidf import TfidfCache
from advanced_prompting_engine.graph.query import GraphQueryLayer
from advanced_prompting_engine.pipeline.runner import PipelineRunner
nodes, edges = build_canonical_graph()
G = nx.DiGraph()
for n in nodes: G.add_node(n['id'], **n)
for e in edges: G.add_edge(e['source_id'], e['target_id'], **e)
ec = EmbeddingCache(); ec.initialize(G)
tc = TfidfCache(); tc.initialize(G)
pipeline = PipelineRunner(G, GraphQueryLayer(G), ec, tc)
result = pipeline.run("Test intent for release validation")
Verify the result has: coordinate (12 faces), active_constructs, tensions, gems (132), spokes (12), central_gem, harmonization_pairs (6), construction_questions (12).
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.
- 7d ago First seen · 77 lines · 0 tokens per session scan A 70fab306a270
pre-release is a command published in the GitHub repository JoshuaRamirez/advanced-prompting-engine (0 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 723 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
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.
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.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.