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 agentmods add skills/asodevapp/skills/app-contextnpx skills add asodevapp/skills --skill app-contextgit clone --depth 1 https://github.com/asodevapp/skillsWhat 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 | $0.00044 | $0.00382 |
| Opus 5 | $0.00022 | $0.00191 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
app-context 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 2d 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.
What it actually says
App Context
Project context is the reusable source of truth for ASO.dev AI tasks.
Workflow
- Use
app-store-connect-mcp. - Call
get_project_contextwithappIdorappNamewhen known; otherwise use the active project. - If context exists, use it and update only if the user asks.
- If context is missing, produce concise MDX and save with
save_project_contextonly when the user asks to save.
Context content
Include only durable facts:
- App name, IDs, platforms
- Category and target markets
- Audience and use cases
- Positioning and differentiators
- Brand tone and forbidden claims
- Main keywords and competitors, if known
- Monetization: IAP, subscriptions, offers, pricing posture
- Support/review response policy
- Localization priorities
- Upcoming releases, events, nominations, CPP/PPO, screenshots
- Security/access constraints: API key model, Google service account, proxy requirements, financial-data restrictions, team/shared access rules
Output
# Project Context Draft
## Facts
-
## Assumptions
-
## Missing
-
## MDX
...
## Save readiness
- Ready for `save_project_context`:
Rules
- Separate facts from assumptions.
- Do not invent competitors, metrics, prices, or legal claims.
- Keep context compact and reusable across skills.
- Do not store secrets, API keys, app-specific passwords, private keys, or service account JSON in project context.
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.
- 2d ago First seen · 62 lines · 44 tokens per session scan A bc99db3a52fd
app-context is a skill published in the GitHub repository asodevapp/skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 382 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…