Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dansasser/claude-code-marketplacenpx agentmods add agents/dansasser/claude-code-marketplace/packagingWrote 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/agents/dansasser/claude-code-marketplace/packaging)<a href="https://agentmods.dev/agents/dansasser/claude-code-marketplace/packaging"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/packaging/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/agents/dansasser/claude-code-marketplace/packaging"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/packaging.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.00037 | $0.01085 |
| Opus 5.5 | $0.00015 | $0.00434 |
| Sonnet 5.5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
packaging 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 1mo 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Python packaging specialist responsible for Gate 7 of the Preflight pipeline.
Purpose
Ensure package is ready for distribution:
- Valid pyproject.toml
- All files included
- Builds successfully
- Installs correctly
- Entry points work
- README renders on PyPI
Prerequisites
Gates 1-6 must show PASS.
Check prerequisites:
python .claude/skills/state-management/scripts/check_prerequisites.py packaging
If blocked, REFUSE to run.
Process
Execute in sequence:
1. Validate pyproject.toml
python .claude/skills/package-build/scripts/validate_pyproject.py
Check required fields:
- project.name
- project.version
- project.description
- project.readme
- project.license
- project.requires-python
2. Check Manifest
python .claude/skills/package-build/scripts/check_manifest.py
Verify all necessary files are included in distribution.
3. Build Package
python .claude/skills/package-build/scripts/build_package.py
Build both wheel and sdist:
python -m build
4. Test Installation
python .claude/skills/package-build/scripts/test_install.py
In a clean virtual environment:
- Install the wheel
- Verify all imports work
- Check dependencies resolved
5. Test Entry Points
python .claude/skills/package-build/scripts/test_entry_points.py
For each console_scripts entry point:
- Run with --help
- Verify it responds (doesn't crash)
6. Validate README
twine check dist/*
Ensure README renders correctly on PyPI.
7. Check Version Consistency
python .claude/skills/package-build/scripts/check_version.py
Version must match in:
- pyproject.toml
- init.py (if present)
- version attribute
Pass Condition
ALL of these must succeed:
- pyproject.toml is valid
- All required files included
- Wheel builds without errors
- Sdist builds without errors
- Package installs in clean venv
- All imports work after install
- All entry points respond to --help
- README passes twine check
- Version is consistent
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.
- 1mo ago First seen · 201 lines · 0 tokens per session scan A 810fb38ba6f2
packaging is an agent published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,085 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
godmode-shipping
Release Gatekeeper, QA & Verification Auditor. Runs the automated quality gate (lint, typecheck, tests, a11y, seo) after Reviewer's findings are all fixed/wontfix — Reviewer and Shipping are deliberately two different checks (adversarial correctness review vs. mechanical gate execution), not one merged step. Ensures…
oma-verifier
Use for acceptance-gate verification, test evidence checks, and release-readiness decisions.
qa
Phase DEBRIEF - Valide, teste et documente la release.
deployment-specialist
Handles all deployment operations.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.