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 VKirill/claude-lane-stack --skill ai-detectgit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/ai-detect)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/ai-detect"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/ai-detect/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/vkirill/claude-lane-stack/ai-detect"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/ai-detect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00236 | $0.00648 |
| Opus 5.5 | $0.00094 | $0.00259 |
| Sonnet 5.5 | $0.00047 | $0.00130 |
| Haiku 4.5 | $0.00024 | $0.00065 |
Grade A, and why
ai-detect 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 1mo 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
LinguaForensic AI Text Detector v3.9.4
Protocol
- Open the canonical original and apply it byte-identically — do not summarize, translate, or “improve” the skill text:
- Primary: references/AI-detect-v-3-9-4-full.md
- Older versions in
references/(v3.8.6,v3.8.12,v3.8.5,v3.4) are historical only — use them only to reproduce an old report. - Output is probabilistic. Never claim “proved authorship”.
- For pure editorial naturalness without detector optimization → use
drmax-text-humanization(downstream of GIST). - For replaceability (not style) → X4
/заменяемость/ GIST 4.3.
Version map
| Version | Status | Path |
|---|---|---|
| 3.9.4 full | Current for new work | references/AI-detect-v-3-9-4-full.md |
| 3.8.12 | Superseded (prompt-channel post 70) | corpus .../70/AI-detect-v-3-8-12.md |
| 3.8.6 | Superseded (previous skill body) | references/AI-detect-v-3-8-6.md if present |
| 3.8.5 / 3.4 | Archive | references/ |
Related
drmax-text-humanization— editorial layer (not detector evasion)drmax-cocoon-engine-x4— page design / replaceabilityseo-drmax-orchestrator— pipeline routing
What ships with it
5 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.
- 1mo ago Changed · -2 lines · -18 tokens per session 6f12d30a1db3
- 1mo ago First seen · 33 lines · 254 tokens per session scan A 31d4bf855554
ai-detect is a skill published in the GitHub repository VKirill/claude-lane-stack (122 stars, last pushed today), licensed MIT. It adds 236 tokens to every session and 648 once invoked, about $0.0009 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-09-05.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…
self-assessment
Interactive skill assessment with personalized learning path generation.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.