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/appboypov/pew-pew-plaza-packsWrote 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/appboypov/pew-pew-plaza-packs/tech-usage-block)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/tech-usage-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/tech-usage-block/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/commands/appboypov/pew-pew-plaza-packs/tech-usage-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/tech-usage-block.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.00000 | $0.00177 |
| Opus 5.5 | $0.00000 | $0.00071 |
| Sonnet 5.5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
tech-usage-block 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.
This is a copy
100% identical to abilities-block — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Block Command
When this command is used, use the following block. Acknowledge your understanding and then await the user's request.
## 🛠️ Tech Usage
> 💡 *Technology preferences, device usage patterns, and digital comfort level of this persona.*
- **Devices**: [List primary devices used (e.g., iPhone 14 Pro, MacBook Air, iPad)]
- **Favorite Apps**: [List frequently used applications (e.g., Slack, Notion, Instagram, Spotify)]
- **Comfort Level**: [Describe technical proficiency (e.g., Tech-savvy power user, Average user, Basic user with limited tech experience)]
- **Digital Habits**: [Describe typical technology usage patterns (e.g., Heavy mobile user, Prefers desktop for work, Multi-device workflow)]
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 · 16 lines · 0 tokens per session scan A d222d72551d9
tech-usage-block is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (87 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 177 tokens. A static security scan graded it A with 0 findings. It is 100% identical to abilities-block, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
generate-design-md
Génère un DESIGN.md à la racine du projet à partir du template Claude Craft + analyse des sources UI existantes (Tailwind, tokens, CSS).
lavra-design
Orchestrate the full design pipeline -- brainstorm, plan, research, revise, review, lock.
bobby-define
Define the product — brief → personas → journeys → feature map, with a gate at each stage.