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/vohongtho/code-intel-platform/backupnpx skills add vohongtho/code-intel-platform --skill backupgit clone --depth 1 https://github.com/vohongtho/code-intel-platformWhat 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.00050 | $0.00868 |
| Opus 5 | $0.00025 | $0.00434 |
| Sonnet 5 | $0.00010 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
backup 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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backup
37 symbols | 2 files | path:
code-intel/core/src/backup/| call density: 0.9/sym
When to Use
Load this skill when:
- The task involves code in
code-intel/core/src/backup/ - The user mentions
constructor,stop,getS3Configor asks how they work - Adding, modifying, or debugging backup-related functionality
- Tracing call chains that pass through the backup layer
Key Files
| File | Symbols | Notes |
|---|---|---|
code-intel/core/src/backup/backup-service.ts |
S3Config, getS3Config, hmac, sha256hex +(24) |
20 exported |
code-intel/core/src/backup/backup-scheduler.ts |
BackupScheduler, constructor, isEnabled, start +(5) |
9 exported |
Entry Points
Start exploration here — exported symbols with no external callers:
constructor(method)→code-intel/core/src/backup/backup-scheduler.ts:18stop(method)→code-intel/core/src/backup/backup-scheduler.ts:58getS3Config(function)→code-intel/core/src/backup/backup-service.ts:26constructor(method)→code-intel/core/src/backup/backup-service.ts:197downloadFromS3(method)→code-intel/core/src/backup/backup-service.ts:327listS3Backups(method)→code-intel/core/src/backup/backup-service.ts:342
Hot Symbols
Sorted by call graph degree (changing these has the highest blast radius):
| Symbol | Kind | In ← | → Out | File |
|---|---|---|---|---|
s3Request |
function | 3 | 8 | backup/backup-service.ts |
createBackup |
method | 4 | 5 | backup/backup-service.ts |
restoreBackup |
method | 3 | 5 | backup/backup-service.ts |
start |
method | 1 | 6 | backup/backup-scheduler.ts |
_runBackups |
method | 1 | 5 | backup/backup-scheduler.ts |
applyRetention |
method | 2 | 4 | backup/backup-service.ts |
_loadIndex |
method | 4 | 2 | backup/backup-service.ts |
BackupService |
class | 4 | 0 | backup/backup-service.ts |
listBackups |
method | 3 | 1 | backup/backup-service.ts |
hmac |
function | 2 | 1 | backup/backup-service.ts |
getBackupKey |
function | 1 | 2 | backup/backup-service.ts |
getS3Config |
method | 3 | 0 | backup/backup-service.ts |
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.
- yesterday First seen · 72 lines · 50 tokens per session scan A 58d6d2ffbb41
backup is a skill published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 868 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…