What is goal-tracker?

A session-goal tracker that records a goal, its items, dates, status, and supporting evidence in a file.

It helps answer what remains, what is parked, what is still open, and whether a session goal is actually finished.

It avoids reconstructing progress from memory and prevents work being marked complete without something that verifies it.

goal-tracker — Skill for Claude Code and Codex by pantheon-org/tekhne

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 pantheon-org/tekhne --skill goal-tracker

Clone the repo

git clone --depth 1 https://github.com/pantheon-org/tekhne

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pantheon-org/tekhne/goal-tracker/github.svg)](https://agentmods.dev/skills/pantheon-org/tekhne/goal-tracker)

Your own site

<a href="https://agentmods.dev/skills/pantheon-org/tekhne/goal-tracker"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/goal-tracker/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pantheon-org/tekhne/goal-tracker"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/goal-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,349 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.

Model	Per session	Once invoked
Fable 5.1	$0.00101	$0.01349
Opus 5.5	$0.00040	$0.00540
Sonnet 5.5	$0.00020	$0.00270
Haiku 4.5	$0.00010	$0.00135

Measured 5d ago against content hash 8a1ed9e53e60, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

goal-tracker 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 5d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/goal.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/project-mgmt/goal-tracker/SKILL.md · 138 lines

How it starts

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

Goal Tracker

Write down the one thing this session is for, keep it honest as work lands, and answer "what's left" without reconstructing it from memory.

Mindset

An unevidenced status is worse than no status. A goal claiming an item is done, with nothing anyone can point at, turns an open question into a false answer and the reader stops checking. Trade convenience for provability everywhere.

Keep trust asymmetric. Close work done inside the repository yourself, since anyone can re-check it. Leave work that left the repository for its owner to close.

When to Use

The user states a goal at session start.
The project requires a goal for every conversation.
The user asks "what's left", "what's outstanding", "are we done".
Park an item, promote an overgrown goal, or close one out.

When Not to Use

Work a plan file already drives. Track it there.
A mechanical request with no end state worth recording.
Deferred work that was never part of a goal. Use create-context-file instead.

Core Rules

Keep exactly one goal active per session. Replace the first or fold it in; never run two.
Demand evidence before done. Park unconfirmed outside work at awaiting.
File a follow-up the same turn you park an item, then delete its row.
Record a promoted goal as promoted. Never as completed.

Workflow

Run the clarity test first. Use socratic-method for a goal with no verifiable end state, and guided-interview when its items hinge on an unmade choice. Otherwise draft it:

./scripts/goal.sh new "Rotate the exposed token and unblock Phase 1"

Pass --session <id> (or GOAL_SESSION) when conversations share the repository.

Check the draft with the user. Start work only once they confirm or correct it.

Set goal-status: in-progress on the first item to gain evidence. Write that evidence in the same turn the item closes. Add a dated log line on every change, and save the file in that turn where the next session reads it, such as the main branch. Keep discovered work as a follow-up unless the end state is unreachable without it.

Read the full file on GitHub · 138 lines

Files

What ships with it

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

5d ago Changed 8a1ed9e53e60
17d ago Changed · +5 lines 92cceb0e88de
1mo ago First seen · 133 lines · 101 tokens per session scan A af73639753b7

Subscribe to this mod's changes

goal-tracker is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 1,349 once invoked, about $0.0004 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-09-15.

Project management agent-skills skills tessl

feature-prioritisation

Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…

mohitagw15856/pm-claude-skills · 103 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

goal-tracker