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/wangyendt/wayne-skills/alapinpx skills add wangyendt/wayne-skills --skill alapigit clone --depth 1 https://github.com/wangyendt/wayne-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/skills/wangyendt/wayne-skills/alapi)<a href="https://agentmods.dev/skills/wangyendt/wayne-skills/alapi"><img src="https://agentmods.dev/badge/skills/wangyendt/wayne-skills/alapi.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 | $0.00154 | $0.00786 |
| Opus 5 | $0.00077 | $0.00393 |
| Sonnet 5 | $0.00031 | $0.00157 |
| Haiku 4.5 | $0.00015 | $0.00079 |
Grade C, and why
alapi scanned grade C 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 4d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
Run `printenv ALAPI_TOKEN` first. How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ALAPI
Overview
Use this skill to work against the full ALAPI OpenAPI catalog without hand-parsing the schema each time. The skill bundles the raw OpenAPI source, a generated endpoint catalog, an auth guide, and a reusable request script.
Workflow
- Confirm whether
ALAPI_TOKENis available. - If the token is missing, tell the user to request one from
https://apifox.com/apihub/, then ask them to send it back. - After the user sends the token, persist it to the active shell profile, export it in the current session, and avoid echoing it back in logs.
- Use
references/intent-router.mdfirst to map a user request to the most likely endpoint with minimal context cost. - Open
references/api-catalog.mdonly for the exact endpoint you selected. - Use
scripts/alapi_request.pyfor real calls instead of rewriting HTTP boilerplate. - If the OpenAPI source changes, replace
references/openapi-source.jsonand rerunscripts/generate_references.py.
Authentication
- ALAPI uses header auth:
token: $ALAPI_TOKEN - All endpoints in the bundled OpenAPI spec use
POST - All endpoints use
application/jsonrequest bodies - Base URL:
https://v3.alapi.cn
Token Handling
Run printenv ALAPI_TOKEN first.
If the token is missing:
- Tell the user to申请或管理 ALAPI token at
https://apifox.com/apihub/ - Ask the user to send the token
- After receiving it, persist it based on the active shell:
zsh: appendexport ALAPI_TOKEN='...'to~/.zshrcbash: appendexport ALAPI_TOKEN='...'to~/.bashrc
- Also export it in the current shell before making API calls
Do not invent or reuse placeholder tokens for real requests.
References
references/auth-and-usage.md: auth model, calling conventions, error-handling checklistreferences/intent-router.md: lowest-cost full routing table from common intent to endpointreferences/api-catalog.md: endpoint-by-endpoint reference including purpose and request schemareferences/openapi-source.json: bundled ALAPI OpenAPI source of truth
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 67 lines · 154 tokens per session scan C a96839fe9adc
alapi is a skill published in the GitHub repository wangyendt/wayne-skills (8 stars, last pushed 8d ago), licensed MIT. It adds 154 tokens to every session and 786 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 1 finding (harvests environment variables). 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…