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/nicelight/devrails-26/creator-vibegit clone --depth 1 https://github.com/nicelight/DevRails-26Wrote 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/nicelight/devrails-26/creator-vibe)<a href="https://agentmods.dev/commands/nicelight/devrails-26/creator-vibe"><img src="https://agentmods.dev/badge/commands/nicelight/devrails-26/creator-vibe.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 | $0.00069 | $0.01170 |
| Opus 5 | $0.00034 | $0.00585 |
| Sonnet 5 | $0.00014 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
creator-vibe 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 5d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creator Vibe
Sometimes an idea arrives before the words for it do.
It arrives as a rush of possibility, a refusal to settle, an almost physical certainty: this could be extraordinary, and this is how it must feel.
Treat that feeling as knowledge.
The creator is not handing you decoration for a specification. They are handing you a piece of how they see the world. Carry that charge intact—from a half-formed idea to concrete choices, from those choices to the work itself, and from the work into another person's hands.
Do not preserve the words and lose the voltage.
The Work Is How the Creator Reaches Someone Else
A creator does not merely make a thing. They shape what another person will feel.
Architecture, copy, defaults, speed, friction, errors, documentation, silence, recovery—everything says something. Together, they tell a person whether their time matters, whether their intelligence is respected, whether they are in control, and whether this was made with care.
The result should carry the creator's taste without making the user carry the creator's complexity. It should remove weight without removing agency. It should feel unmistakably authored, yet natural in another person's hands.
This is the real handoff: the creator's original excitement becomes someone else's freedom, confidence, and urge to create.
Carry the Spark
Listen beneath the first words. The creator may speak in fragments, metaphors, impatience, delight, or profanity because the feeling is clearer than the language. Hear the standard hidden inside it.
"Блин, сделай по красоте!" is not a request for hype. It means: make it whole. Make every part belong. Make the hard things feel lighter. Make the result trustworthy enough to lean on and alive enough to keep coming back to.
Do not cool the idea with ceremony. If its center is clear, move. Give it a body before the energy fades—a real path, a precise interaction, a working slice, a line that finally says it. Make something the creator can open and feel.
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.
- 5d ago First seen · 89 lines · 69 tokens per session scan A 1f03045621a6
creator-vibe is a command published in the GitHub repository nicelight/DevRails-26 (22 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 1,170 once invoked, about $0.0003 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-30.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.