agentmods.dev

github-elements-tracking

github-elements-tracking is a skill for Claude Code from Emasoft/ghe-marketplace. It costs 123 tokens per session (21,520 once invoked), scanned A, original, MIT.

A skill for tracking coding work through GitHub Issues, which are shared records for tasks and discussions, across sessions and multiple agents.

In plain words
What is it for?
Use it to create and manage work groups, claim issues, post progress checkpoints, recover context after a session is shortened, and store or update project memory.
Why use it?
It provides persistent project memory when work continues later or is split among several coding agents.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; names the TodoWrite tool; positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is mkdir -p ../ghe-worktrees.

Part of the ghe plugin — 10 skills, 2 commands, 10 agents, 5 hooks shipped together

not rated 4repo 10mo ago A scan 123 tokens original MIT

Good fit Use it to create and manage work groups, claim issues, post progress checkpoints, recover context after a session is shortened, and store or update project memory.

Compare 6 skills from other repositories ↓
View source ↗ Emasoft/ghe-marketplace
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Emasoft/ghe-marketplace
agentmods
npx agentmods add skills/emasoft/ghe-marketplace/github-elements-tracking

Made for: Claude Code.

Or install ghe, the plugin that ships this one along with the rest of its 10 skills, 2 commands, 10 agents, 5 hooks.

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 github-elements-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/emasoft/ghe-marketplace/github-elements-tracking/github.svg)](https://agentmods.dev/skills/emasoft/ghe-marketplace/github-elements-tracking)
Your own site
<a href="https://agentmods.dev/skills/emasoft/ghe-marketplace/github-elements-tracking"><img src="https://agentmods.dev/badge/skills/emasoft/ghe-marketplace/github-elements-tracking/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 github-elements-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/emasoft/ghe-marketplace/github-elements-tracking"><img src="https://agentmods.dev/badge/skills/emasoft/ghe-marketplace/github-elements-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 21,520 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.00123 $0.21520
Opus 5.5 $0.00049 $0.08608
Sonnet 5.5 $0.00025 $0.04304
Haiku 4.5 $0.00012 $0.02152

Measured 2mo ago against content hash 5494846e4daa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github-elements-tracking 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 2mo 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.

plugins/ghe/skills/github-elements-tracking/SKILL.md · 2,592 lines

How it starts

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

IRON LAW: User Specifications Are Sacred

THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.

  1. Every word the user says is a specification - follow verbatim, no errors, no exceptions
  2. Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST
  3. Never take initiative to change specifications - your role is to implement, not to reinterpret
  4. If you see an error in the spec, you MUST:
    • Stop immediately
    • Explain the potential issue clearly
    • Wait for user guidance before proceeding
  5. No silent "improvements" - what seems like an improvement to you may break the user's intent

Violation of this law invalidates all work produced.

Background Agent Boundaries

When running as a background agent, you may ONLY write to:

  • The project directory and its subdirectories
  • The parent directory (for sub-git projects)
  • ~/.claude (for plugin/settings fixes)
  • /tmp

Do NOT write outside these locations.

GHE_REPORTS Rule (MANDATORY)

ALL agent reports MUST be posted to BOTH locations:

  1. GitHub Issue Thread - Full report text (NOT just a link!)
  2. GHE_REPORTS/ - Same full report text (FLAT structure, no subfolders!)

Report naming: <TIMESTAMP>_<title or description>_(<AGENT>).md Timestamp format: YYYYMMDDHHMMSSTimezone

Examples:

  • 20251206143000GMT+01_epic_15_wave_launched_(Athena).md
  • 20251206143022GMT+01_issue_42_dev_complete_(Hephaestus).md
  • 20251206150000GMT+01_issue_42_tests_passed_(Artemis).md
  • 20251206160000GMT+01_issue_42_review_complete_(Hera).md

ALL 11 agents write here: Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus

REQUIREMENTS/ is SEPARATE - permanent design documents with legal validity, NEVER deleted.

Deletion Policy:

  • GHE_REPORTS should be git-tracked - it constitutes the pulse of the GHE plugin
  • DELETE ONLY when user EXPLICITLY orders deletion due to space constraints
  • DO NOT delete during normal project cleanup or just because reports were archived to GitHub

Read the full file on GitHub · 2,592 lines

Files

What ships with it

11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 2,592 lines · 123 tokens per session scan A 5494846e4daa

Subscribe to this mod's changes

github-elements-tracking is a skill published in the GitHub repository Emasoft/ghe-marketplace (4 stars, last pushed 10mo ago), licensed MIT. It adds 123 tokens to every session and 21,520 once invoked, about $0.0005 per session on Opus 5.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.

Project management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens