agentmods.dev

eve-repo-upkeep

eve-repo-upkeep is a skill for Claude Code, Codex from Incept5/eve-skillpacks. It costs 20 tokens per session (812 once invoked), scanned A, original, MIT.

A maintenance guide for Eve-compatible app repositories. It checks repository files, agent instructions, and code for outdated Eve conventions before updating them.

In plain words
What is it for?
Use it to review and update an Eve manifest, skills list, maintainer instructions, agent configuration, and related code. It is also useful when preparing a major deployment or onboarding a new maintainer.
Why use it?
It helps keep a repository usable after Eve platform or manifest changes. It also highlights stale configuration, obsolete entries, deprecated commands, and inline secrets before a release or handover.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

not rated 0repo 2mo ago A scan 20 tokens original MIT

Good fit Use it to review and update an Eve manifest, skills list, maintainer instructions, agent configuration, and related code. It is also useful when preparing a major deployment or onboarding a new maintainer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/incept5/eve-skillpacks/eve-repo-upkeep
View source ↗ Incept5/eve-skillpacks
Install

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.

Any agent
npx skills add Incept5/eve-skillpacks --skill eve-repo-upkeep
Clone the repo
git clone --depth 1 https://github.com/Incept5/eve-skillpacks

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for eve-repo-upkeep

README.md
[![agentmods](https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-repo-upkeep/github.svg)](https://agentmods.dev/skills/incept5/eve-skillpacks/eve-repo-upkeep)
Your own site
<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-repo-upkeep"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-repo-upkeep/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.

agentmods 80×15 button for eve-repo-upkeep

Your own site · 80×15
<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-repo-upkeep"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-repo-upkeep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 812 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00812
Opus 5 $0.00010 $0.00406
Sonnet 5 $0.00004 $0.00162
Haiku 4.5 $0.00002 $0.00081

Measured 12d ago against content hash a8d493334a17, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

eve-repo-upkeep 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 12d 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.

eve-se/eve-repo-upkeep/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Eve Repo Upkeep

Keep an app repo current with Eve conventions. The checks are independent — run them in parallel when multiple areas need attention.

When to Use

  • After Eve platform updates or manifest schema changes
  • Before a major deploy or release
  • When onboarding a new maintainer

Phase 1: Assess

Quickly determine which areas need attention. Check which of these files exist and whether they look stale — don't deep-read every file, just note which areas need work:

  • .eve/manifest.yaml — does it exist? Is the schema line eve/compose/v1?
  • skills.txt — does it exist? Are there pinned or obsolete entries?
  • AGENTS.md / CLAUDE.md — do they reference current skills?
  • agents/ directory — do agents.yaml, teams.yaml, chat.yaml exist?
  • Codebase — any obvious deprecated CLI patterns or inline secrets?

If only one area needs work, handle it directly. Otherwise, proceed to Phase 2.

Phase 2: Dispatch Workers

Create one worker per area that needs updating. Each worker description below is self-contained — a worker can execute its area independently without context from the others.

Worker: Manifest Alignment

Check and fix .eve/manifest.yaml:

  • Ensure schema: eve/compose/v1 is present.
  • Prefer services: over legacy components:.
  • Keep x-eve ingress and pipeline definitions accurate.
  • Keep x-eve.defaults in sync with harness defaults (harness/profile/options).
  • Keep x-eve.agents profiles aligned with orchestration policy.
  • Ensure x-eve.agents.config_path and x-eve.chat.config_path point to valid files.
  • Confirm ${secret.KEY} usage for secrets.
  • Deploy pipelines should include a build step before release.
  • Services with Docker images should have build.context defined.
  • Registry auth secrets (REGISTRY_USERNAME + REGISTRY_PASSWORD) are required only for custom BYO registries.

Worker: Skills File

Check and fix skills.txt:

  • Keep Eve skillpack references up to date.
  • Remove obsolete packs or pinned versions.

Read the full file on GitHub · 93 lines

Changes

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.

  1. 12d ago First seen · 93 lines · 20 tokens per session scan A a8d493334a17

Subscribe to this mod's changes

eve-repo-upkeep is a skill published in the GitHub repository Incept5/eve-skillpacks (0 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 812 once invoked, about $0.0001 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-31.

DevOps and cloud
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens