pstack-claude is a set of opinionated coding-agent skills and workflows ported from Cursor to Claude Code, Codex, Pi, and other agent harnesses. It guides agents toward concise, simple, and verified code by routing goals to suitable workflows and supporting subagent tools. The catalogue entries are the project's skills, agents, hook, and plugin implementations for these agent environments.
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 michael-denyer/pstack-claude --skill principle-migrate-callers-then-delete-legacy-apisgit clone --depth 1 https://github.com/michael-denyer/pstack-claudeWrote 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/michael-denyer/pstack-claude/principle-migrate-callers-then-delete-legacy-apis)<a href="https://agentmods.dev/skills/michael-denyer/pstack-claude/principle-migrate-callers-then-delete-legacy-apis"><img src="https://agentmods.dev/badge/skills/michael-denyer/pstack-claude/principle-migrate-callers-then-delete-legacy-apis/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/michael-denyer/pstack-claude/principle-migrate-callers-then-delete-legacy-apis"><img src="https://agentmods.dev/badge/skills/michael-denyer/pstack-claude/principle-migrate-callers-then-delete-legacy-apis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00045 | $0.00128 |
| Opus 5.5 | $0.00018 | $0.00051 |
| Sonnet 5.5 | $0.00009 | $0.00026 |
| Haiku 4.5 | $0.00005 | $0.00013 |
Grade A, and why
principle-migrate-callers-then-delete-legacy-apis 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 15d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- principle-migrate-callers-then-delete-legacy-apis — 100% identical, 0 lines differ
- principle-migrate-callers-then-delete-legacy-apis — 91% identical, 12 lines differ
- principle-migrate-callers-then-delete-legacy-apis — 91% identical, 2 lines differ
- principle-migrate-callers-then-delete-legacy-apis — 91% identical, 0 lines differ
- principle-migrate-callers-then-delete-legacy-apis — 89% identical, 9 lines differ
- principle-migrate-callers-then-delete-legacy-apis — 88% identical, 10 lines differ
- principle-migrate-callers-then-delete-legacy-apis — 88% identical, 10 lines differ
- principle-migrate-callers-then-delete-legacy-apis — 88% identical, 10 lines differ
What it actually says
Migrate Callers Then Delete Legacy APIs
- Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details
When this applies:
- No external users depend on backward compatibility
- The project can absorb coordinated breaking changes
- The new API is part of a simplification or refactor initiative
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.
- 15d ago Changed · -8 lines 7a4af874d91f
- 1mo ago Changed 8014f4eb04fe
- 2mo ago First seen · 23 lines · 45 tokens per session scan A 14c88d4c3c9c
principle-migrate-callers-then-delete-legacy-apis is a skill published in the GitHub repository michael-denyer/pstack-claude (3,667 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 128 once invoked, about $0.0002 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-30.
Other skills, from other repositories
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
fastapi-templates
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
api-design-principles
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.