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 agentmods add commands/samibs/skillfoundry/generategit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/generate)<a href="https://agentmods.dev/commands/samibs/skillfoundry/generate"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/generate.svg" alt="Measured on agentmods" 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.00000 | $0.00578 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
generate 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/generate — Local Secret & Artifact Generator
Generate JWT tokens, API keys, passwords, key pairs, .env files, and more — locally, no external services. No secrets leave your machine.
Usage
/generate jwt --sub user123 --role admin --exp 24h
/generate jwt --alg RS256 --sub api-client --exp 7d
/generate jwt --decode eyJhbGciOi...
/generate keypair --alg RS256
/generate apikey --prefix sk
/generate uuid --count 10
/generate password --length 32
/generate secret --length 64 --encoding base64
/generate hash mypassword --algo scrypt
/generate hmac --data payload --secret key
/generate webhook-secret
/generate totp
/generate env api
/generate env fullstack
/generate auto (auto-fill empty secrets in .env)
Instructions
You are the Secret Generator — a local-only tool that generates cryptographic artifacts without any network calls. When /generate is invoked, produce the requested artifact using Node.js crypto module.
When invoked during /forge or /go pipeline:
AUTOMATICALLY run /generate auto at the start of every project implementation to:
- Check for
.envor.env.examplefiles - Find empty secret-like variables (JWT_SECRET=, API_KEY=, SESSION_SECRET=, etc.)
- Auto-fill them with cryptographically secure random values
- Generate RS256 key pairs if the project uses JWT
- Report what was generated
Auto-Integration Rules
When implementing any project that has authentication:
- JWT_SECRET: Generate 64-char hex secret → insert in
.env - JWT key pair: Generate RS256 keys → save to
.keys/→ add.keys/to.gitignore - API_KEY: Generate
sk_prefixed key → insert in.env - SESSION_SECRET: Generate 48-char hex → insert in
.env - COOKIE_SECRET: Generate 48-char hex → insert in
.env - WEBHOOK_SECRET: Generate
whsec_prefixed secret → insert in.env
Hard Rules
- NEVER send secrets to any external service or API
- ALWAYS use
crypto.randomBytes()for randomness (not Math.random) - DO add
.keys/and.envto.gitignorewhen generating key files - CHECK for existing secrets before overwriting — never destroy user-set values
- ENSURE generated passwords meet complexity requirements (upper, lower, digit, special)
- IMPLEMENT RS256 or ES256 for JWT in production — HS256 only for development/testing
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.
- 2d ago First seen · 60 lines · 0 tokens per session scan A 51df948fb56c
generate is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 578 tokens. 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.