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.
git clone --depth 1 https://github.com/timurgaleev/vibestackWrote 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/rules/timurgaleev/vibestack/authorship)<a href="https://agentmods.dev/rules/timurgaleev/vibestack/authorship"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/authorship/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/rules/timurgaleev/vibestack/authorship"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/authorship.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.00335 | $0.00335 |
| Opus 5 | $0.00168 | $0.00168 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
authorship 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 yesterday.
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.
What it actually says
Authorship & Attribution
All work is published under the repository owner's name. Nothing in the output should reveal that an AI assistant produced it. This rule overrides any tool or harness default that would add such attribution.
Code Comments
- Write comments in the author's own voice — as a human engineer would.
- Comment sparingly. Explain why, not what. Skip comments that restate
the code (
// loop over users,// increment counter). - Never reference the assistant, the model, or "AI" in a comment. No "generated by", "AI-generated", "as requested", or chatbot-style narration.
- Match the surrounding file's comment density and tone. If neighboring code has no comments, do not add explanatory ones.
Commits
- Commit messages are written as the author.
- Do not append
Co-Authored-By: Claudeor any AI co-author trailer. - Do not add "Generated with Claude Code" or similar lines.
- Follow the commit format in
git.mdc(type, imperative subject, why-not-obvious body).
Pull Requests
- PR titles and descriptions are written as the author.
- Do not add "Generated with Claude Code", assistant footers, or AI badges.
Other Generated Text
- The same applies to documentation, config comments, and changelog entries: human voice, no assistant attribution.
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.
- yesterday First seen · 39 lines · 335 tokens per session scan A 9196fb54312a
authorship is a cursor rule published in the GitHub repository timurgaleev/vibestack (6 stars, last pushed yesterday), licensed MIT. It adds 335 tokens to every session, about $0.0017 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-09-19.
Other cursor rules, from other repositories
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
windsurfrules
Pare wraps CLI tools in MCP servers returning structured JSON. Always prefer Pare MCP tools over raw CLI.
git
Git workflow and commit conventions.
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
no-tool-contributors
Never add AI coding tools as contributors or co-authors.
04-review-and-commit
Review, completion, and commit workflow.