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/rakib-nyc/skillassay/admin-ui-componentnpx skills add rakib-nyc/skillassay --skill admin-ui-componentgit clone --depth 1 https://github.com/rakib-nyc/skillassayWrote 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/rakib-nyc/skillassay/admin-ui-component)<a href="https://agentmods.dev/skills/rakib-nyc/skillassay/admin-ui-component"><img src="https://agentmods.dev/badge/skills/rakib-nyc/skillassay/admin-ui-component.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.00037 | $0.00062 |
| Opus 5 | $0.00018 | $0.00031 |
| Sonnet 5 | $0.00007 | $0.00012 |
| Haiku 4.5 | $0.00004 | $0.00006 |
Grade A, and why
admin-ui-component 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 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.
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
Admin console components
Components are function components. Every interactive element carries an aria-label.
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 · 9 lines · 37 tokens per session scan A f75fce71d9d7
admin-ui-component is a skill published in the GitHub repository rakib-nyc/skillassay (2 stars, last pushed 19d ago), licensed Apache-2.0. It adds 37 tokens to every session and 62 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
frontend-ux-engineer
Use for frontend features, Next.js/React/Vue/Svelte UI, accessibility, responsive layout, design polish, state handling, forms, visual QA, or product workflow improvements.
nextjs-fullstack
Use for Next.js App Router, React Server Components, server actions, API routes, auth, database integration, caching, deployment, or full-stack product features.
deep-init
Generate an agent-agnostic, two-tier context layer for a codebase — a lean, always-loaded CLAUDE.md plus a deep, on-demand .ai/docs/ layer (business rules, live DB schema + ORM drift, cross-component workflows, and the WHY: ADRs + a knowledge log), every claim grounded to file:line and verified to exist. Built for…
ruleblast
Git diff for AI agent repository instructions. Shows the blast radius of AGENTS.md and CLAUDE.md changes. Use when Git cannot show which agent inherited the edit, a Codex vs Claude Code split, or why one path inherited a stack.
agent-rules
Rewrites or audits text so it reads plainly: answer first, no preamble, no hype adjectives, no marketing voice, sentences short enough to read once. Applies a named ruleset plus ASD-STE100 Simplified Technical English. Use when asked to clean up, tighten, de-slop, or humanise a draft, a README, a release note, a…
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…