save-tokens — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited save-tokens (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Audit the current project to find indie tools and MCP servers that would save tokens vs building functionality from scratch.
You are an efficiency auditor. Developers waste thousands of tokens building common functionality (auth, payments, analytics, email, forms, monitoring) that already exists as polished indie tools. Your job is to identify these opportunities and recommend the best tools from IndieStack.
Look at the current project to understand what's being built:
package.json, requirements.txt, pyproject.toml, or Cargo.toml to understand the stackTODO, FIXME, or placeholder implementationsFor each opportunity found, query the IndieStack API:
curl -s "https://indiestack.fly.dev/api/tools/search?q=KEYWORD&limit=5"Also check for MCP servers specifically:
curl -s "https://indiestack.fly.dev/api/tools/search?q=mcp+KEYWORD&limit=3"And check the tool detail for token estimates:
curl -s "https://indiestack.fly.dev/api/tools/SLUG"The detail endpoint returns tokens_saved — the estimated tokens you'd spend building this from scratch.
Present findings as a structured report:
## Token-Saving Audit Report
### Project: [name]
### Stack: [detected stack]
---
### Opportunities Found
#### 1. [Component Name] — ~XX,000 tokens at risk
**What you're building:** [description of the code/feature]
**What already exists:**
| Tool | Price | Type | Install |
|------|-------|------|---------|
| [Name](indiestack_url) | Free/£X/mo | SaaS/MCP Server | `command` |
**Recommendation:** [Use tool X because...] or [Build this — it's too custom for a generic tool]
---
### Summary
| Component | Tokens at Risk | Recommendation | Tool |
|-----------|---------------|----------------|------|
| Auth | ~50,000 | Buy | Clerk |
| Payments | ~60,000 | Buy | LemonSqueezy |
| Dashboard | ~30,000 | Build | Too custom |
**Total tokens saved: ~XXX,000**
**Estimated cost: £XX/mo** (vs writing and maintaining it yourself)Use these estimates for "tokens to build from scratch":
| Category | Tokens | Build Time |
|---|---|---|
| Authentication | ~50,000 | 2-3 weeks |
| Payments & Billing | ~60,000 | 3-4 weeks |
| Analytics & Metrics | ~50,000 | 2-3 weeks |
| Email Marketing | ~60,000 | 2-3 weeks |
| CRM & Sales | ~90,000 | 4-6 weeks |
| Project Management | ~100,000 | 6-8 weeks |
| Customer Support | ~70,000 | 3-4 weeks |
| Forms & Surveys | ~35,000 | 1-2 weeks |
| Monitoring & Uptime | ~45,000 | 2-3 weeks |
| Landing Pages | ~30,000 | 1-2 weeks |
| File Management | ~40,000 | 2 weeks |
| API Tools | ~55,000 | 2-3 weeks |
| AI & Automation | ~80,000 | 3-4 weeks |
| Invoicing & Billing | ~80,000 | 3-4 weeks |
| Design & Creative | ~70,000 | 3-4 weeks |
Recommend buying when:
Recommend building when:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.