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.
git clone --depth 1 https://github.com/zhanyoulin456/seevin-claude-pluginsWrote 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/commands/zhanyoulin456/seevin-claude-plugins/jsd-auto-lint)<a href="https://agentmods.dev/commands/zhanyoulin456/seevin-claude-plugins/jsd-auto-lint"><img src="https://agentmods.dev/badge/commands/zhanyoulin456/seevin-claude-plugins/jsd-auto-lint/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/commands/zhanyoulin456/seevin-claude-plugins/jsd-auto-lint"><img src="https://agentmods.dev/badge/commands/zhanyoulin456/seevin-claude-plugins/jsd-auto-lint.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00006 | $0.01432 |
| Opus 5 | $0.00003 | $0.00716 |
| Sonnet 5 | $0.00001 | $0.00286 |
| Haiku 4.5 | $0.00001 | $0.00143 |
Grade A, and why
jsd-auto-lint 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
执行步骤
- 如果用户没有提供上下文,则默认获取当前分支修改的文件,否则按照用户提供的：$ARGUMENTS参数进行处理，只处理当前分支的所有改动代码
- 检查第一步获取的所有文件是否符合jsd - 企业通用规范,具体规则查看下方，但是不要吹毛求疵
- 生成一份报告到项目根目录.code-lint-report.md,查看下方的末班
- 这份报告是给开发者查看的,同时需要作为下一步让agent修复的参考
code-lint-report 模板
问题1
文件名:[filename]
路径:path
违反规则:[rule-name]
问题简述:[problem-short-desc]
问题代码摘录: [problem-code]
解决方案:[solution]
问题2
.......
总结
[summary]
jsd - 企业通用规范
1. 基本命名规范
目录命名
● 规范：全小写，多单词以中划线连接。集合类文件夹采用复数命名。
● 示例： components, views, utils, user-manage
文件命名
● 通用文件： 小写字母 + 中划线（detail.vue,index.js, user-auth.ts, company.png）
● Vue单文件： 业务页面用小写中划线（user-list.vue）
● 公共组件：项目级或模块级均需管理在 src/components文件夹中，对于复杂度高的组件目录下采用大驼峰文件夹形式，内建 index.vue，复杂度低的组件可直接components/PageTitle.vue
示例：
-
- 在src/components文件夹
- 1.1 复杂组件：采用大驼峰文件夹形式，内建 index.vue(src/components/ComplexComponent/index.vue)
- 1.2 简单组件：直接在components文件夹下，文件名采用小写中划线形式（components/PageTitle.vue）
-
- 在src/views文件夹
- 2.1 业务页面：采用小写中划线形式（src/views/page/user-list.vue）
2. 路由与页面映射
在vue项目中为了实现“路径即代码”的可维护性，建立以下强约束：
● 映射规则： 路由 path 必须与 src/views 目录下的文件层级完全一致
● 地址 /user/order-list --> 对应文件 src/views/user/order-list/index.vue
● 懒加载： 所有路由定义必须使用 () => import() 动态导入
2.编码规范
2.1 HTML & Vue Template
● 缩进： 统一使用 2个空格。
● 语义化： 优先使用 nav, main, section 等标签，避免“满屏 div”
● 组件引用： 自定义组件使用大驼峰 ，强制 自闭合
● 属性值： 必须使用双引号包裹
● 注释： 表示模块开始表示模块结束
● CSS选择器：使用单词字母小写，多个单词组成时，采用中划线-分隔，符合BEM/Vue官方风格，
● Vue SFC 推荐 scoped 或 CSS Modules，减少命名冲突
2.2 CSS 规范
● 预处理器： 使用 scss/less
● 层级嵌套： 原则上 不得超过三层
● 变量管理： 颜色、字号尽量使用全局定义的css变量,避免直接定义颜色值
● 原子化： 鼓励使用 tailwind.css 处理布局与间距，减少无意义的类名
● 禁止随意在项目中增加全局样式
● 避免编写行类样式（内联样式）
● 避免使用标签名、直接子选择器
● 省略 0 后面的单位
● 合理使用scss的特性进行代码优化
2.3 Javascript 规范
● 统一使用单引号（''）
● 变量使用camelCase 方式命名，尽可能使用完整的单词拼写命名，不要嫌单词长
● 方法名、参数名、局部变量都统一使用小驼峰 lowerCamelCase 风格，方法应当使用常用的add、update、delete、get、handle等作为前缀连接处理的对象进行命名
● 提炼函数：当一个函数内代码量过大时，需抽离函数
● 遵循卫语句优先原则
● 把复杂的条件分支语句提炼成函数
● 三目运算符不能嵌套过深（两层是可以接受的程度）
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.
- 9d ago First seen · 162 lines · 6 tokens per session scan A a1e43b844912
jsd-auto-lint is a command published in the GitHub repository zhanyoulin456/seevin-claude-plugins (4 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 1,432 once invoked, about $0.0000 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.