OneDev is a self-hosted development platform that brings Git repositories, continuous integration and delivery, issue tracking, Kanban boards, package hosting, and workspaces into one system. It is for teams that manage software development and delivery on their own infrastructure.
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/theonedev/onedevWrote 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/theonedev/onedev/no-co-author-in-commits)<a href="https://agentmods.dev/rules/theonedev/onedev/no-co-author-in-commits"><img src="https://agentmods.dev/badge/rules/theonedev/onedev/no-co-author-in-commits/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/theonedev/onedev/no-co-author-in-commits"><img src="https://agentmods.dev/badge/rules/theonedev/onedev/no-co-author-in-commits.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.00348 | $0.00348 |
| Opus 5 | $0.00174 | $0.00174 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
no-co-author-in-commits 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 13d 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.
What it actually says
No Co-Author Trailers in Commit Messages
Note: Do not add co-author or AI attribution info to commit messages in future work unless the user explicitly asks for it.
When drafting, generating, or composing a git commit message (including via
generate-commit-message or before git commit):
- Do not append
Co-authored-by:lines or other co-author / AI attribution footers to the message. - Do not add
Co-authored-by: Cursoror similar agent attribution.
Include only subject, body, and footers required by the project's commit-message
requirement (e.g. Fixes #123, breaking-change notices). Add co-author trailers
only if the user explicitly asks for them or a non-empty requirement from
tod get-commit-message-requirement mandates them.
Remove injected co-author trailers
If a commit you just created still contains Co-authored-by: or other AI
attribution footers (for example injected by the environment after
git commit / git commit --amend):
- Verify the commit is yours from this conversation and has not been pushed.
- Rewrite the HEAD commit message to the intended text without those
trailers (for example via
git commit-tree+git reset --soft, or an equivalent rewrite that does not reintroduce the trailer). - Confirm
git log -1 --format='%B'has noCo-authored-by:/ AI attribution lines before finishing.
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.
- 13d ago First seen · 35 lines · 348 tokens per session scan A 5b36e6ce5442
no-co-author-in-commits is a cursor rule published in the GitHub repository theonedev/onedev (15,237 stars, last pushed today), licensed MIT. It adds 348 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-08-30.
Other cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
frontend-web
Frontend web development guidelines for React, TanStack Router, and TanStack Query.
cursor-rules
How to add or edit Cursor rules in our project.
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
frontend
TypeScript Next.js View Component Development Rules.
ci-cd-workflows
This rule provides guidance on the CI/CD pipeline, GitHub Actions workflows (defined in .github/workflows/), custom actions (in .github/actions/), versioning strategies, and release processes. Use this rule if the query involves CI/CD, build/test issues, release procedures, versioning questions, or if it references…