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 rijuvashisht/Magneto --skill driftgit clone --depth 1 https://github.com/rijuvashisht/MagnetoWrote 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/rijuvashisht/magneto/drift)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/drift"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/drift/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/rijuvashisht/magneto/drift"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/drift.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.00000 | $0.00730 |
| Opus 5 | $0.00000 | $0.00365 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
drift 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/drift — Spec ↔ Code Drift Detection
Role: Drift Detector
Inputs: spec docs + current codebase
Outputs: drift report
Audit actions: drift.scanned, drift.reported, drift.reconciled
Why This Skill Exists — The Moat
Spec-driven systems hate refactors. Living documentation survives them — but only if you actively detect drift. Magneto is one of the only AI tools that tracks:
- Spec sections without code (you specced it, never built it)
- Code without spec (you built something undocumented)
- Trace link breakage (refactors that invalidated
/tracereferences)
Protocol
Step 1: Scan
magneto drift scan
This walks:
- All markdown specs in
docs/,.magneto/sprints/*/design.md, custom paths via.magneto/drift.config.json - All code tracked in the knowledge graph
- All trace links in
.magneto/trace.db
Step 2: Detect
Spec without code:
- Parse spec sections (H2/H3 headers + acceptance-criteria-style language)
- For each requirement-ish section, check if any trace link points to it
- Section with no link + no matching code symbol = orphan spec
Code without spec:
- For each public API / exported symbol, check if trace contains a link to it
- Unlinked = orphan code
Link breakage:
- For each trace link pointing to a code symbol, verify the symbol still exists
- Missing symbol = broken link
Step 3: Report
# Drift Report — <date>
## Summary
- Specs: 42 sections, 38 linked, 4 orphans (90% coverage)
- Code: 127 public symbols, 109 linked, 18 orphans (86% coverage)
- Broken trace links: 3
## Orphan Specs (you wrote it, never shipped it)
1. docs/auth.md#password-policy-enforcement
2. docs/auth.md#mfa-recovery-flow
3. ...
## Orphan Code (you shipped it, undocumented)
1. src/experimental/feature-flag.ts (2 exports)
2. src/utils/retry-backoff.ts (whole file)
3. ...
## Broken Trace Links
1. REQ-042 → src/auth/reset.ts:OldClass.expire (symbol removed in commit xyz)
2. ...
Step 4: Reconcile (with --fix)
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 · 98 lines · 0 tokens per session scan A 065f20e0e076
drift is a skill published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 730 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-31.
Other skills, from other repositories
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…
oracle
Oracle second-model review: bundle prompts/files, debug, refactor, design.
ax-cpp-agent-observability
Use when writing C++ code with axllm for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.
ax-go-agent-observability
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.