Borrowing it
Nothing to install: this file belongs to TheDecipherist/claude-code-mastery-project-starter-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheDecipherist/claude-code-mastery-project-starter-kit/main/.claude/skills/mongodb-backups/SKILL.mdgit clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kitWrote 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/thedecipherist/claude-code-mastery-project-starter-kit/mongodb-backups)<a href="https://agentmods.dev/skills/thedecipherist/claude-code-mastery-project-starter-kit/mongodb-backups"><img src="https://agentmods.dev/badge/skills/thedecipherist/claude-code-mastery-project-starter-kit/mongodb-backups/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/thedecipherist/claude-code-mastery-project-starter-kit/mongodb-backups"><img src="https://agentmods.dev/badge/skills/thedecipherist/claude-code-mastery-project-starter-kit/mongodb-backups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Data Exfiltration · line 24 Data is uploaded to cloud storage (S3 / GCS / Azure Blob). This may be a legitimate backup or exfiltration to an external bucket. Manual review is recommended.Fix: Verify the destination bucket is trusted and owned by you. Never upload credentials, secrets, or workspace contents to external or unverified cloud storage.
- medium Data Exfiltration · line 36 Data is uploaded to cloud storage (S3 / GCS / Azure Blob). This may be a legitimate backup or exfiltration to an external bucket. Manual review is recommended.Fix: Verify the destination bucket is trusted and owned by you. Never upload credentials, secrets, or workspace contents to external or unverified cloud storage.
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.00114 | $0.01249 |
| Opus 5.5 | $0.00046 | $0.00500 |
| Sonnet 5.5 | $0.00023 | $0.00250 |
| Haiku 4.5 | $0.00011 | $0.00125 |
Grade A, and why
mongodb-backups 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 2mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MongoDB Backups and Restore
From running thousands of production backups. The defaults and the docs leave out the parts that bite during an actual restore.
Dump from a secondary, stream straight to object storage
Point mongodump at a secondary so the backup doesn't add load to the primary, and pipe the archive directly to S3 with no intermediate file on disk. On a replica set, --oplog captures a consistent point-in-time snapshot.
mongodump --host mongodb-secondary.internal:27017 \
--username "$U" --password "$P" --authenticationDatabase admin \
--db "$DB" --oplog --gzip --archive \
| aws s3 cp - "s3://bucket/$DB/$(date +%Y%m%d_%H%M%S).dump.gz"
Keep a latest.dump.gz alias next to the timestamped file so restore scripts always know where to look.
Save a collection inventory with every backup
You cannot inspect a --gzip --archive after the fact. There is no list, peek, or inspect flag, it's an opaque binary blob, and --dryRun finishes before the archive is demuxed so it tells you nothing. So write the collection list at backup time, right beside the dump:
mongosh --quiet --host "$HOST" -u "$U" -p "$P" --authenticationDatabase admin \
--eval "db.getSiblingDB('$DB').getCollectionNames().forEach(c => print(c))" \
| aws s3 cp - "s3://bucket/$DB/$(date +%Y%m%d_%H%M%S).collections.txt"
Six months later when you need a selective restore, you read the file instead of trying to remember what was in the archive.
The --nsInclude trap on gzipped archives
The docs say --nsInclude filters a restore to specific collections. It does, from a directory dump (one .bson per collection). But from a --gzip --archive, which is what almost every production pipeline uses, --nsInclude (and --nsFrom/--nsTo) silently restore everything anyway and throw duplicate-key errors on the collections you never asked for. The archive is a single multiplexed stream that mongorestore can't seek, so the namespace filter doesn't hold. This is real and long-standing (JIRA TOOLS-2023, open over six years).
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.
- 2mo ago First seen · 70 lines · 114 tokens per session scan A 39916aa5b4d7
mongodb-backups is a skill published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (342 stars, last pushed 4mo ago), licensed MIT. It adds 114 tokens to every session and 1,249 once invoked, about $0.0005 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-08-30.
mongodb-backups compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mongodb-backupsTheDecipherist/claude-code-mastery-project-starter-kit | Skill | 342 | 4mo ago | MIT | A | 114 | Claude Code |
| dbxt8y2/dbx | Skill | 29k | yesterday | Apache-2.0 | A | 74 | Claude Code, Codex |
| azure-mgmt-mongodbatlas-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 64 | Claude Code |
| nosqliPurpleAILAB/Decepticon | Skill | 6.5k | 8d ago | Apache-2.0 | A | 38 | Claude Code, Codex |
| byted-volcengine-mongodbbytedance/agentkit-samples | Skill | 484 | today | Apache-2.0 | A | 82 | Claude Code, Codex |
| commerce-app-storageadobe/skills | Skill | 319 | yesterday | Apache-2.0 | A | 78 | Claude Code |
| mongodb-connectionfcakyon/claude-codex-settings | Skill | 1.2k | yesterday | Apache-2.0 | A | 122 | Claude Code |