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/catch-the-wave/fullstack-ios-claude-skillsWrote 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/catch-the-wave/fullstack-ios-claude-skills/landing)<a href="https://agentmods.dev/commands/catch-the-wave/fullstack-ios-claude-skills/landing"><img src="https://agentmods.dev/badge/commands/catch-the-wave/fullstack-ios-claude-skills/landing.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.00014 | $0.00920 |
| Opus 5 | $0.00007 | $0.00460 |
| Sonnet 5 | $0.00003 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade B, and why
landing scanned grade B with 1 finding 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 8d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Output Instructions How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Generation
Generate a landing page text for a product targeting a specific segment using the structure below.
Input Required
Please provide:
- Segment description and jobs: {description of the segment with their Core Jobs, Big Jobs, criteria}
- Product description: {product description with link to website}
If you don't have this information, I can help you generate it using the /ajtbd-b2b-segments or /ajtbd-b2c-segments commands first.
Landing Page Structure
1. Oneliner
[What] + [Core Job] + [value]
Example: "Personal driver service to safely get your kids to school without worrying"
2. Core Value Proposition
[Core Job] + [value] + [how it's delivered through features]
Example: "Get your kids to school safely and on time through verified drivers, real-time tracking, and automated scheduling"
Key Micro Jobs:
- [Micro Job 1]
- [Micro Job 2]
- [Micro Job 3]
3. Aha-Moment Section
[Allow experiencing the easiest first Micro Job]
How to experience the aha-moment:
- [Way to experience aha-moment 1]
- [Way to experience aha-moment 2]
4. Value Communication
Communicate value for each job:
- [Value 1 for Core Job 1/Micro Job 1]
- [Value 2 for Core Job 2/Micro Job 2]
- [Value 3 for Core Job 3/Micro Job 3]
- [Value 4 for Core Job 4/Micro Job 4]
5. Recognition Section
Do you recognize yourself?
Do you want [Big Job 1]? Or [Big Job 2]?
Triggers:
- [Trigger 1]?
- [Trigger 2]?
Emotions at point A:
- [Emotion at point A 1]?
- [Emotion at point A 2]?
Problems at point A:
- [Problem at point A 1]?
- [Problem at point A 2]?
6. How It Works
How you'll complete [Core Job 1]:
- [Micro Job 1] + [Value received when performing Micro Job 1]
- [Micro Job 2] + [Value received when performing Micro Job 2]
- [Micro Job 3] + [Value received when performing Micro Job 3]
- [Micro Job 4] + [Value received when performing Micro Job 4]
[Repeat for each Core Job if there are multiple]
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.
- 8d ago First seen · 141 lines · 14 tokens per session scan B dae6d02043cf
landing is a command published in the GitHub repository catch-the-wave/fullstack-ios-claude-skills (5 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 920 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.