rotate-secret
Skill0 starsChanged 5 months agoMITView on GitHub
Replace a bot's token or webhook URL safely, whether it leaked or you just want a fresh one. Use this when the user runs /rotate-secret, or says a token or webhook leaked, was exposed, or needs changing, resetting, or rotating. Regenerates it on the platform's side, updates the .env, restarts the bot, and makes sure the old secret is dead.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- flavien-ia/hypervibe-harnesstheir own version, first seen Nov 15, 2026
- acegalaxy-co/ace_commons-ccswitch-clitheir own version, first seen Nov 1, 2026
- kanalias/ace_commons-ccswitch-clitheir own version, first seen Nov 1, 2026
- flavien-ia/hypervibe-crafttheir own version, first seen Oct 25, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- flavien-ia/hypervibe-craft★ 52same name
- flavien-ia/hypervibe-harness★ 52same name
- acegalaxy-co/ace_commons-ccswitch-cli★ 3same name
- kanalias/ace_commons-ccswitch-cli★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bot-styleSkill
- check-botSkill
- deploy-to-cloudSkill
- deploy-to-hostSkill
- discord-styleSkill
- edit-botSkill
- keep-runningSkill
- list-botsSkill
- make-botSkill
- package-botSkill
- remove-botSkill
- security-checkSkill
- skillsSkill
- telegram-styleSkill
- test-botSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If no bot was named above, look in the bots/ folder (older bots may sit at the project root.
- Distinctive: line 28
If the secret leaked, the priority is to kill the exposed one quickly.
- Distinctive: line 44
When the user pastes the new secret, write it into .env for them, replacing the old value.
- Distinctive: line 50
Make sure the old secret is truly dead: for a Discord full bot or a Telegram bot, Reset Token or /revoke already did that.
- Distinctive: line 57
Keep it plain and beginner-friendly.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
rotate-secret
Replace a bot's one secret safely and make sure the old one can no longer be used. The bot may be a Discord or a Telegram bot; read the matching style skill (discord-style for Discord, telegram-style for Telegram) once you know which, so you know what kind of secret it uses.
Talk to the user as if they are not a programmer. Use plain language. Never print or repeat the secret itself; only write it into .env when the user pastes it.
The bot whose secret to rotate, and whether it leaked:
$ARGUMENTS
Work through these in order.
- If no bot was named above, look in the bots/ folder (older bots may sit at the project root; check there too), list the bots by name, and ask which one's secret to rotate. Wait.
- Work out the platform and which kind of secret the bot uses: a Discord bot token (full bot), a Discord webhook URL (webhook poster), or a Telegram BotFather token (either Telegram shape). The steps differ.
- If the secret leaked, the priority is to kill the exposed one quickly. Say so, and treat speed as more important than avoiding a few minutes of downtime.
- Regenerate the secret on the platform's side, walking the user through it in plain language:
- Discord full bot: open the Discord Developer Portal, open this bot's application, go to the Bot section, and click Reset Token. This instantly kills the old token and gives a new one, so the bot will be down until the new token is in place. Have them copy the new token.
- Discord webhook poster: webhooks cannot be reset in place. If it leaked, delete the old webhook now (channel settings, Integrations, Webhooks) so the exposed URL dies, then create a new webhook and copy its URL. If it did not leak and you want zero downtime, create the new webhook first, then delete the old one after the switch.
- Telegram (either shape): open BotFather, send /revoke and pick this bot (or use /mybots, select the bot, then API Token, then Revoke current token). This instantly kills the old token and gives a new one, so the bot will be down until the new token is in place. Have them copy the new token.
- When the user pastes the new secret, write it into .env for them, replacing the old value. Never display it.
- Restart the bot so it uses the new secret: if it runs under PM2, restart it there
(pm2 restart
<name>); otherwise stop it and start it again with npm start from the bot's folder. - Make sure the old secret is truly dead: for a Discord full bot or a Telegram bot, Reset Token or /revoke already did that; for a Discord webhook, confirm the old webhook has been deleted.
- Finish in plain language with no emoji: confirm the bot is back up on the new secret and the old one no longer works, and remind the user never to paste a token or webhook URL anywhere, since that is what makes rotating necessary.
Keep it plain and beginner-friendly. Never include or show the secret anywhere except writing it into .env.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

