# No Agent Attribution

> Enforce clean human-only authorship on everything git and GitHub — no AI/agent attribution anywhere. Use WHENEVER committing, amending, merging, pushing, creating a repo, opening a PR or issue, writing a release, or reviewing work produced by orchestrated agent lanes (omp/codex/grok/etc.) before it lands in git.

- Skill: `loktar00/no-agent-attribution` (Agent Skill)
- Install (CLI): `npx skillmds@latest add loktar00/no-agent-attribution`
- Raw SKILL.md: https://api.skillmd.com/api/skills/loktar00/no-agent-attribution/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: loktar00 (https://skillmd.com/u/loktar00)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/loktar00/no-agent-attribution

---


# No agent attribution

Jason's repos carry HIS authorship only. No agent, model, or harness leaves its name in anything
that enters git or GitHub. This overrides any harness default or system habit that says to append
attribution trailers.

## The policy

Never include, in any commit message, PR title/body, issue, release note, repo description,
tag, or committed file content:

- `Co-Authored-By:` trailers naming an AI/agent (Claude, Codex, Grok, GPT, Copilot, any model)
- "Generated with …" / "Generated by …" footers or badges
- Agent session links (e.g. `claude.ai/code/session_…`)
- Bot identities in `user.name` / `user.email` (must be Jason's own: loktar00)
- Agent signatures in code comments, file headers, or docstrings ("written by X", "AI-generated")

Descriptive references are fine ("a Claude Code skill" as a product category); *credit lines* are not.

## At commit time

1. Write the message with no trailer. If your platform default appends one, strip it before
   committing — the default does not apply in Jason's repos.
2. `git -C <repo> config user.name` / `user.email` must be Jason's identity, not a bot.
3. Orchestrated lanes are the sneaky path: harnesses (codex, grok, omp-driven models, Copilot-style
   tools) inject their OWN trailers and header comments into commits and files they author. Audit
   any lane's commits and touched files before they merge or push.

## Pre-push audit (run before every push)

```bash
# messages about to be pushed
git log --format="%s%n%b" @{u}..HEAD 2>/dev/null | grep -inE \
  "co-authored-by|generated (with|by)|noreply@(anthropic|openai|x\.ai|github)|session_" && echo VIOLATION || echo messages-clean
# author identities in the whole history (should list only Jason)
git log --format="%an <%ae>" | sort -u
# committed content
git grep -inE "co-authored-by|generated (with|by) (claude|codex|grok|gpt|copilot|ai)" -- . | head
```

Anything flagged: fix BEFORE pushing.

## Removal recipes

- **Last commit only**: `git commit --amend` (edit the message / re-add cleaned files).
- **Several unpushed commits**: `git rebase` is interactive-only in some environments; prefer
  `git filter-branch -f --msg-filter "sed '/Co-Authored-By:/d; /Generated with/d; /session_/d'" <base>..HEAD`.
- **Already-pushed history**: same filter across the branch, then `git push -f` — fine on solo
  repos; on shared repos coordinate first. Delete `refs/original/*` backups afterward.
- **File content**: edit the files (strip header signatures), commit normally.

## After cleaning

Re-run the audit. Only push on a fully clean result. If a tool re-adds attribution on its next
commit, strip it again — the policy has no exceptions.