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/axiotn/frontend-page-generator/api-clientnpx skills add AXIOTN/frontend-page-generator --skill api-clientgit clone --depth 1 https://github.com/AXIOTN/frontend-page-generatorWrote 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/axiotn/frontend-page-generator/api-client)<a href="https://agentmods.dev/skills/axiotn/frontend-page-generator/api-client"><img src="https://agentmods.dev/badge/skills/axiotn/frontend-page-generator/api-client.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.00000 | $0.00981 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
api-client scanned grade A 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, { How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API 客户端子技能
概述
提供统一的 API 客户端封装,包含请求、缓存、错误处理等功能。
API 客户端类
class ApiClient {
constructor(baseURL, options = {}) {
this.baseURL = baseURL;
this.timeout = options.timeout || 10000;
this.headers = {
'Content-Type': 'application/json',
...options.headers
};
}
async request(endpoint, options = {}) {
const url = `${this.baseURL}${endpoint}`;
const controller = new AbortController();
const timeoutId = setTimeout(() => controller.abort(), this.timeout);
try {
const response = await fetch(url, {
...options,
headers: { ...this.headers, ...options.headers },
signal: controller.signal
});
clearTimeout(timeoutId);
if (!response.ok) throw await this.handleError(response);
return await response.json();
} catch (error) {
clearTimeout(timeoutId);
throw this.normalizeError(error);
}
}
get(endpoint, params) {
const query = params ? `?${new URLSearchParams(params)}` : '';
return this.request(`${endpoint}${query}`);
}
post(endpoint, data) {
return this.request(endpoint, { method: 'POST', body: JSON.stringify(data) });
}
put(endpoint, data) {
return this.request(endpoint, { method: 'PUT', body: JSON.stringify(data) });
}
delete(endpoint) {
return this.request(endpoint, { method: 'DELETE' });
}
}
错误处理
const errorMessages = {
400: '请求参数错误',
401: '未授权,请重新登录',
403: '没有权限执行此操作',
404: '请求的资源不存在',
408: '请求超时,请稍后重试',
500: '服务器错误,请稍后重试',
502: '服务暂时不可用',
503: '服务维护中,请稍后重试'
};
export function handleApiError(error, showMessage = true) {
const status = error.status || 500;
const message = error.message || errorMessages[status] || '未知错误';
if (status === 401) {
localStorage.removeItem('token');
window.location.href = '/login';
return;
}
if (showMessage) console.error(`[API Error ${status}]:`, message);
return { status, message };
}
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.
- 5d ago First seen · 163 lines · 0 tokens per session scan A 74b445611058
api-client is a skill published in the GitHub repository AXIOTN/frontend-page-generator (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 981 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…