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/abdullah4ai/apple-developer-toolkit/asc-wall-submitnpx skills add Abdullah4AI/apple-developer-toolkit --skill asc-wall-submitgit clone --depth 1 https://github.com/Abdullah4AI/apple-developer-toolkitWhat 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.00067 | $0.00506 |
| Opus 5 | $0.00034 | $0.00253 |
| Sonnet 5 | $0.00013 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
asc-wall-submit 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 3d 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
asc wall submit
Use this skill to add or update a Wall of Apps entry without introducing new CLI surface area.
When to use
- User wants to submit an app to the Wall of Apps
- User wants to update an existing Wall of Apps entry
- User asks for the exact Wall submission flow
Required inputs
Collect and confirm all fields before running commands:
app: app namelink: app URL (http/https, usually App Store URL)creator: GitHub handle or creator nameplatform: comma-separated labels (for example:iOS,macOS)
If any value is missing, ask for it first.
Submission workflow
- Run commands from the
App-Store-Connect-CLIrepository root. - Run:
make generate app APP="Your App Name" LINK="https://apps.apple.com/app/id1234567890" CREATOR="your-handle" PLATFORM="iOS,macOS" - Verify generated changes include:
docs/wall-of-apps.jsonREADME.md
- Review diff and confirm:
- The JSON entry is added or updated correctly.
- The README wall snippet is regenerated from markers.
- Open a focused PR with only the Wall-related generated changes.
Guardrails
- Do not hand-edit the Wall snippet in
README.md. - Do not modify unrelated entries in
docs/wall-of-apps.json. - If generation fails due to invalid input, fix inputs and rerun the generator.
- Keep submission path PR-based unless maintainers define an issue-based intake flow.
Examples
Add new app:
make generate app APP="My App" LINK="https://apps.apple.com/app/id1234567890" CREATOR="my-handle" PLATFORM="iOS"
Update existing app (same app name updates in place):
make generate app APP="My App" LINK="https://apps.apple.com/app/id1234567890" CREATOR="my-handle" PLATFORM="iOS,macOS"
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.
- 3d ago First seen · 56 lines · 67 tokens per session scan A 16b41e5b50d7
asc-wall-submit is a skill published in the GitHub repository Abdullah4AI/apple-developer-toolkit (10 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 506 once invoked, about $0.0003 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…