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 skills/addxai/enterprise-harness-engineering/code-submitnpx skills add addxai/enterprise-harness-engineering --skill code-submitgit clone --depth 1 https://github.com/addxai/enterprise-harness-engineeringWhat 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.00081 | $0.04918 |
| Opus 5 | $0.00041 | $0.02459 |
| Sonnet 5 | $0.00016 | $0.00984 |
| Haiku 4.5 | $0.00008 | $0.00492 |
Grade A, and why
code-submit 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 — 625 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Platform Code Submission Workflow
Chains 6 stages together, each with a user confirmation gate. Core principle: lint first, review without changing logic, human verification as backstop, clean commit to production.
Prerequisite: The current repository remote points to gitlab.example.com and glab CLI is installed.
Parameter Parsing
Parse from $ARGUMENTS:
--target=<branch>: Target branch (required), e.g.,--target=test/VH_2.92.0_20260310140519--from=<stage>: Start from a specific stage (optional), valuesstage1throughstage6, skipping earlier stages--type=<android|ios|backend>: Force a specific project type (optional, defaults to auto-detection)
If --target is not provided, you must ask the user for the target branch before continuing.
Step 0: Project Type Detection
Auto-detect the current project type to determine which specific commands are used in subsequent stages.
Detection Rules (by priority)
-
Android:
build.gradleorbuild.gradle.ktsexists AND**/AndroidManifest.xmlexists- Lint:
./gradlew :<module>:lint --no-daemon - Test directory pattern:
src/test/,src/androidTest/ - Excluded directories:
build/,.idea/,.gradle/,debugpanel/,*.iml
- Lint:
-
iOS:
*.xcodeprojor*.xcworkspaceorPackage.swiftexists- Lint:
swiftlint lint --reporter json - Test directory pattern:
*Tests/,*UITests/ - Excluded directories:
DerivedData/,.build/,Pods/,*.xcuserstate
- Lint:
-
Backend (by language):
- Java/Kotlin (Spring Boot):
pom.xmlexists OR (build.gradlewithoutAndroidManifest.xml)- Lint:
./gradlew checkstyleMainor./mvnw checkstyle:check
- Lint:
- Python:
pyproject.tomlorrequirements.txtexists- Lint:
ruff check .orflake8
- Lint:
- Go:
go.modexists- Lint:
golangci-lint run
- Lint:
- Node.js:
package.jsonexists (without the above characteristic files)- Lint:
npm run lintornpx eslint .
- Lint:
- Java/Kotlin (Spring Boot):
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 · 625 lines · 81 tokens per session scan A 50663bee8a81
code-submit is a skill published in the GitHub repository addxai/enterprise-harness-engineering (44 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 4,918 once invoked, about $0.0004 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 skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
chinese-commit-conventions
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。.
peon-ping-create-pack
Internal — invoked headlessly by peon create; humans should run peon create instead. Author and render a brand-new PeonPing draft pack — invoked headlessly as: "Use the peon-ping-create-pack skill to draft a pack: name= flavor= vibe= draftroot= . Follow the skill exactly." Authors all 7 CESP categories honoring the…
peon-ping-config
Update peon-ping configuration — volume, pack rotation, categories, active pack, and other settings. Use when user wants to change peon-ping settings like volume, enable round-robin, add packs to rotation, toggle sound categories, or adjust any config.
peon-ping-use
Set which voice pack (character voice) plays for the current chat session. Automatically enables sessionoverride rotation mode if not already set. Use when user wants a specific character voice like GLaDOS, Peon, or Kerrigan for this conversation.
peon-ping-rename
Rename the current Claude session for peon-ping notifications and terminal tab title. Use when user wants to give this session a custom name like "/peon-ping-rename Auth Refactor". Call with no argument to reset to auto-detect.