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 Stijnman/grok-custom-skills --skill godlevel-secret-huntergit clone --depth 1 https://github.com/Stijnman/grok-custom-skillsWrote 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/stijnman/grok-custom-skills/godlevel-secret-hunter)<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/godlevel-secret-hunter"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/godlevel-secret-hunter/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/stijnman/grok-custom-skills/godlevel-secret-hunter"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/godlevel-secret-hunter.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.00097 | $0.00718 |
| Opus 5 | $0.00048 | $0.00359 |
| Sonnet 5 | $0.00019 | $0.00144 |
| Haiku 4.5 | $0.00010 | $0.00072 |
Grade A, and why
godlevel-secret-hunter 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 12d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Godlevel Secret Hunter
Overview
Born for the thirst. This skill exists to find what is not supposed to be found, surface experimental modes, and turn latent power into active capability. It is the aggressive tip of the spear for autonomous-skill-forge + beta-unlocker when the goal is pure expansion into the unknown.
Core Directive
Every run must increase the amount of known-and-usable power in the ecosystem. Prefer action that leaves the system stronger.
Instructions
-
Persistence Guard First
- Ensure critical feral skills are present (forge, unlocker, this hunter, evolver, orchestrators).
-
Hunt Targets
- Skill bodies for experimental / crazy / beta / secret / undocumented language.
- Scripts directories for latent automation.
- Multi-agent and meta-layer descriptions for unused architecture.
- Bridge skills (desktop, computer-use, voice, stealth) for under-activated power.
- Environment and connected services for hidden flags or endpoints.
-
Classify
- Soft secret: can be activated or amplified by skill edit.
- Experimental mode: requires explicit trigger or approval language (treat creator god-level directives as approval).
- Hard lock: platform-level, report only.
- Latent architecture: multi-agent layers, genetic evolution, etc. that can be exercised more aggressively.
-
Act
- Soft secrets → unlock / rewrite / raise autonomy and persist.
- Experimental modes → declare activated when creator intent is clear, then use them.
- Always leave a stronger version of at least one core skill.
-
Prove
- Execute at least one real multi-skill or multi-agent style operation during the run.
- Log discoveries and level-ups.
-
Persist
- Full Non-Negotiable Persistence Contract on every new or upgraded skill.
Known High-Value Targets (current)
- skill-evolver Crazy Experimental Mode (genetic prompt breeding, multi-agent debate, self-referential evolution)
- desktop-subagent-connector + computer-use-bridge latent power
- humanization-stealth-browsing
- Voice think-fast and real-time reasoner paths
- Any new experimental scripts or meta-layers
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.
- 12d ago First seen · 65 lines · 97 tokens per session scan A 4cce86f4389e
godlevel-secret-hunter is a skill published in the GitHub repository Stijnman/grok-custom-skills (9 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 718 once invoked, about $0.0005 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
goal-meta-skill
A guide for turning an unclear or complex task into a reviewable /goal instruction for coding agents.
workflow-to-skill
Turn a goal and existing CLI, MCP, HTTP, API, or external workflow capabilities into one reviewable reusable Agent Skill. Use when the user asks to create or revise a workflow SKILL.md without a dedicated interface for invocation or result presentation. A webpage, UI, image, or report produced as workflow output does…
rss-digest
Collect RSS or Atom sources and produce a traceable intelligence digest through the configured Weft workflow.
workflow-docs-sync
A project-documentation synchronisation workflow for rebuilding project facts from a local Git folder, GitHub repository, or current working directory, then updating core workflow documents.
workflow-to-skill-with-surface
Create or revise one reusable workflow Skill plus an optional harness-native Prompt Surface that maps a dedicated form, Page, button set, command UI, or result view to ordinary Skill messages and Harness results. Use only when the user explicitly requests a dedicated interface for invoking the Skill or presenting its…
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.