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 bishopZ/2026-Boilerplate --skill hidden-admin-authgit clone --depth 1 https://github.com/bishopZ/2026-BoilerplateWrote 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/bishopz/2026-boilerplate/hidden-admin-auth)<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/hidden-admin-auth"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/hidden-admin-auth/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/bishopz/2026-boilerplate/hidden-admin-auth"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/hidden-admin-auth.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.00037 | $0.01240 |
| Opus 5.5 | $0.00015 | $0.00496 |
| Sonnet 5.5 | $0.00007 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
hidden-admin-auth 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 1mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hidden Admin Auth Setup
Use this skill when you want to keep /product as a private admin utility. It sets up env-driven auth; the operator rotates credentials by updating .env using instructions in .envTemplate.
CRITICAL: Security Rules
Credentials exist ONLY in .env. The skill never receives or writes credentials. It sets up infrastructure; the operator updates .env themselves using instructions in .envTemplate.
| File | Allowed | Forbidden |
|---|---|---|
.env |
Operator updates manually (gitignored) | Skill does not modify |
.envTemplate |
Template values: ADMIN_USERNAME=test + salt/hash for test |
Any real credentials |
| Code (auth.ts, playwright.config, etc.) | Read from process.env; no hardcoded creds |
Any credentials |
| Docs (AGENTS.md, README, AUTHENTICATION.md, playwright/README) | Generic text: "configure via .env", "template default: test/test" | Actual credentials or password hints |
| CHANGELOG | Generic: "credentials moved to env vars" | Any credentials or password hints |
Goal
- Move auth to env vars (
ADMIN_USERNAME,ADMIN_PASSWORD_SALT,ADMIN_PASSWORD_HASH). - Add
.envTemplatewith safe template values (test/test) and instructions for the operator to update.env. - Remove the login link from the public header.
- Update docs generically—never expose credentials.
Files To Update
1) src/server/services/auth.ts
- Read admin user from
process.env.ADMIN_USERNAME,ADMIN_PASSWORD_SALT,ADMIN_PASSWORD_HASH. - If these env vars are set, use them for
verifyUser. Otherwise fall back to the existingfakeUser(test/test) for backwards compatibility. - Remove or keep
fakeUseronly as fallback when env vars are absent.
2) .envTemplate
Add the Hidden Admin Auth block only if it does not exist. Use these template values:
ADMIN_USERNAME=testADMIN_PASSWORD_SALTandADMIN_PASSWORD_HASH: generate for passwordtestusing the hash command.- Optional:
TEST_USERNAMEandTEST_PASSWORD(for E2E when credentials differ from template; defaults totest/test).
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.
- 1mo ago First seen · 115 lines · 37 tokens per session scan A 12a50a630927
hidden-admin-auth is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,240 once invoked, about $0.0001 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.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
record-upgrade-instructions
Record upgrade instructions alongside a Prisma 8 breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma 8 extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.