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/kubev2v/forklift-console-plugin/backend-analyzernpx skills add kubev2v/forklift-console-plugin --skill backend-analyzergit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWrote 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/kubev2v/forklift-console-plugin/backend-analyzer)<a href="https://agentmods.dev/skills/kubev2v/forklift-console-plugin/backend-analyzer"><img src="https://agentmods.dev/badge/skills/kubev2v/forklift-console-plugin/backend-analyzer.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.01701 |
| Opus 5 | $0.00000 | $0.00851 |
| Sonnet 5 | $0.00000 | $0.00340 |
| Haiku 4.5 | $0.00000 | $0.00170 |
Grade A, and why
backend-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Analyzer Skill
Invoke with: "analyze backend", "refresh backend knowledge", "update backend expert", "scrape forklift backend"
Purpose
Systematically analyze the Forklift Go backend codebase (kubev2v/forklift) and generate structured knowledge files as .mdc Cursor rules under .cursor/rules/backend/.
Configuration
- Forklift repo path: Set by
state.jsonfieldforkliftRepoPath(default:../forkliftrelative to this repo) - Target branch:
upstream/main - Output directory:
.cursor/rules/backend/ - State file:
.cursor/skills/backend-analyzer/state.json
Modes
Full Analysis (first run or forced refresh)
Run all 6 phases sequentially. Within each phase, launch parallel subagents.
Incremental Refresh
- Read
state.jsonforlastAnalyzedCommit - Run
git fetch upstreamin the forklift repo - Run
git diff --name-only <lastCommit>..upstream/mainto find changed files - Map changed files to domain areas using the domain-to-path mapping below
- Re-run analysis only for affected domains
- Update
state.json
Domain-to-Path Mapping
| Domain file | Source paths in forklift repo |
|---|---|
architecture.mdc |
cmd/forklift-controller/, pkg/controller/controller.go, pkg/controller/base/, cmd/forklift-api/ |
api-types.mdc |
pkg/apis/forklift/v1beta1/ |
providers/provider-controller.mdc |
pkg/controller/provider/controller.go, pkg/controller/provider/validation.go, pkg/controller/provider/container/doc.go, pkg/controller/provider/web/doc.go, pkg/controller/provider/web/provider.go |
providers/vsphere.mdc |
pkg/controller/provider/container/vsphere/, pkg/controller/provider/model/vsphere/, pkg/controller/provider/web/vsphere/ |
providers/ovirt.mdc |
pkg/controller/provider/container/ovirt/, pkg/controller/provider/model/ovirt/, pkg/controller/provider/web/ovirt/ |
providers/openstack.mdc |
pkg/controller/provider/container/openstack/, pkg/controller/provider/model/openstack/, pkg/controller/provider/web/openstack/ |
providers/ova.mdc |
pkg/controller/provider/container/ova/, pkg/controller/provider/model/ovf/, pkg/controller/provider/web/ova/, pkg/controller/ova/ |
providers/hyperv.mdc |
pkg/controller/provider/container/hyperv/, pkg/controller/provider/model/hyperv/, pkg/controller/provider/web/hyperv/, pkg/controller/hyperv/ |
providers/ec2.mdc |
pkg/provider/ec2/ |
providers/ocp.mdc |
pkg/controller/provider/container/ocp/, pkg/controller/provider/model/ocp/, pkg/controller/provider/web/ocp/ |
plans/plan-controller.mdc |
pkg/controller/plan/controller.go, pkg/controller/plan/validation.go, pkg/controller/plan/context/, pkg/controller/plan/ensurer/, pkg/controller/plan/util/, pkg/controller/migration/ |
plans/plan-adapters.mdc |
pkg/controller/plan/adapter/ |
plans/migration-pipeline.mdc |
pkg/controller/plan/migration.go, pkg/controller/plan/kubevirt.go, pkg/controller/plan/handler/, pkg/controller/plan/migrator/ |
plans/scheduler.mdc |
pkg/controller/plan/scheduler/ |
mappings/network-map.mdc |
pkg/controller/map/network/ |
mappings/storage-map.mdc |
pkg/controller/map/storage/ |
infrastructure/webhooks.mdc |
pkg/forklift-api/webhooks/ |
infrastructure/rest-api.mdc |
pkg/forklift-api/services/, pkg/controller/provider/web/ |
infrastructure/virt-v2v.mdc |
pkg/virt-v2v/ |
infrastructure/shared-libraries.mdc |
pkg/lib/ |
infrastructure/monitoring.mdc |
pkg/monitoring/, pkg/metrics/ |
infrastructure/host-controller.mdc |
pkg/controller/host/ |
infrastructure/hook-controller.mdc |
pkg/controller/hook/ |
operator/operator.mdc |
operator/ |
What ships with it
1 file 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.
- 5d ago First seen · 159 lines · 0 tokens per session scan A 95773544a4f4
backend-analyzer is a skill published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,701 tokens. 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
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…