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 skills add znlgis/opengis-skills --skill admin-net-frontendgit clone --depth 1 https://github.com/znlgis/opengis-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/znlgis/opengis-skills/admin-net-frontend)<a href="https://agentmods.dev/skills/znlgis/opengis-skills/admin-net-frontend"><img src="https://agentmods.dev/badge/skills/znlgis/opengis-skills/admin-net-frontend/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/znlgis/opengis-skills/admin-net-frontend"><img src="https://agentmods.dev/badge/skills/znlgis/opengis-skills/admin-net-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 82 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 83 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 84 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.1 | $0.00098 | $0.03747 |
| Opus 5.5 | $0.00039 | $0.01499 |
| Sonnet 5.5 | $0.00020 | $0.00749 |
| Haiku 4.5 | $0.00010 | $0.00375 |
Grade A, and why
admin-net-frontend 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目地址（上游）： https://github.com/zuohuaijun/Admin.NET
znlgis 维护分支： https://github.com/znlgis/Admin.NET
前端代码目录：
Web/（Vue3 应用）当前版本： v2.4.x（
Web/package.json为 2.4.33；upstreamv2分支最后提交 2026-01-30，znlgis 维护v2分支最后提交 2026-03-26，后者已升到 Vite 8 / vue-router 5.0.3；截至 2026-10 实测）在线文档： https://adminnet.top/
演示环境： https://demo.adminnet.top（账号：superAdmin.NET / 密码：Admin.NET++010101）
许可证： Apache-2.0（upstream 仓库 LICENSE）
概述
Admin.NET 前端基于 vue-next-admin 模板二次开发，采用 Vue 3 Composition API + TypeScript + Element Plus + Vite 7 技术栈。项目提供完整的企业级中后台管理界面，包括登录认证、动态菜单/路由、RBAC 权限控制、多语言、主题切换、SignalR 实时通讯等能力。
核心技术栈（版本对齐 upstream v2/master 的 Web/package.json，截至 2026-10 实测）：
- 框架： Vue 3.5+（Composition API +
<script setup>） - 语言： TypeScript 5.9
- 构建： Vite 7+（znlgis 维护分支已升到 Vite 8）/ pnpm 10
- UI 组件： Element Plus 2.x
- 路由： Vue Router 5（upstream 5.0.0，znlgis 分支 5.0.3）
- 状态管理： Pinia 3
- 国际化： vue-i18n 11
- HTTP 客户端： Axios
- 图表： ECharts 6
- 实时通讯： @microsoft/signalr
项目结构
Web/
├── public/ # 公共静态资源
├── lang/ # 国际化语言文件
├── api_build/ # API 代码自动生成脚本
├── scripts/ # 构建辅助脚本
├── src/
│ ├── api/ # 手写 API 调用（axios 封装）
│ ├── api-services/ # 自动生成的 API 服务（对应后端 Swagger）
│ ├── api-plugins/ # 插件相关的 API 服务
│ ├── assets/ # 静态资源（图片、样式）
│ ├── components/ # 全局公共组件
│ ├── directive/ # 自定义指令（如权限指令）
│ ├── layout/ # 布局组件（侧边栏、头部、标签页等）
│ ├── router/ # 路由配置
│ ├── stores/ # Pinia 状态管理
│ ├── theme/ # 主题样式
│ ├── types/ # TypeScript 类型定义
│ ├── utils/ # 工具函数
│ ├── views/ # 页面视图
│ │ ├── login/ # 登录页
│ │ ├── home/ # 首页/仪表盘
│ │ ├── system/ # 系统管理页面集合
│ │ ├── approvalFlow/ # 审批流程
│ │ ├── mqttx/ # MQTT 客户端
│ │ ├── elive/ # 视频监控
│ │ ├── about/ # 关于页
│ │ └── error/ # 错误页（403/404/500）
│ ├── App.vue # 根组件
│ └── main.ts # 应用入口
├── index.html # HTML 入口
├── package.json # 依赖配置
├── vite.config.ts # Vite 构建配置
├── tsconfig.json # TypeScript 配置
├── eslint.config.mjs # ESLint 配置
├── .prettierrc.cjs # Prettier 配置
├── .env # 通用环境变量
├── .env.development # 开发环境变量
└── .env.production # 生产环境变量
What ships with it
2 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.
- today Changed · +10 lines · +49 tokens per session d80761111cf1
- 12d ago Changed · +12 lines f4dd9b370b75
- 13d ago Changed · +37 lines 34181233c022
- 1mo ago Changed · +2 lines 6f697023fca0
- 1mo ago Changed 59e60fc7776a
- 1mo ago Changed · -330 lines f0b5f1bfc2af
- 1mo ago First seen · 562 lines · 49 tokens per session scan A 20406c1a7255
admin-net-frontend is a skill published in the GitHub repository znlgis/opengis-skills (75 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 3,747 once invoked, about $0.0004 per session on Opus 5.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-30.
Other skills, from other repositories
vue
Vue 3 - Progressive JavaScript framework with Composition API, reactivity system, single-file components, Vite integration, TypeScript support.
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
v3-upsert-route
A route configuration helper for projects that keep their routes in `src/router/index.ts`. It creates or updates permanent and permission-controlled pages, including titles, icons, and child routes.
v3-upsert-store
A workflow for creating or updating Pinia stores, which are shared state modules in Vue applications. It requires the store name, state fields, types, initial values, persistence choices, and actions.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
v3-use-utils
Documentation for reusable utility functions in a project, including validation, date formatting, CSS variables, permissions, local storage, and tokens.