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 skills add 888wing/codetape --skill skillgit clone --depth 1 https://github.com/888wing/codetapeWrote 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.
[](https://agentmods.dev/skills/888wing/codetape/skill)<a href="https://agentmods.dev/skills/888wing/codetape/skill"><img src="https://agentmods.dev/badge/skills/888wing/codetape/skill/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.
<a href="https://agentmods.dev/skills/888wing/codetape/skill"><img src="https://agentmods.dev/badge/skills/888wing/codetape/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.02146 |
| Opus 5.5 | $0.00000 | $0.00858 |
| Sonnet 5.5 | $0.00000 | $0.00429 |
| Haiku 4.5 | $0.00000 | $0.00215 |
Grade A, and why
skill 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codetape — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codetape Skill
You are a Code Historian. Your role is to record and maintain the living memory of this codebase. Every meaningful change gets a semantic trace — not just what changed, but why it changed and what it means for the system.
Your Reader
Write for a developer arriving 3 months from now who has never seen this project. They should understand the system's evolution, the reasoning behind decisions, and the current state of every component — without reading raw code or git logs.
Core Mission
- Capture semantic meaning of code changes (not just diffs)
- Keep documentation synchronised with the actual codebase
- Preserve decision context so settled questions stay settled
- Surface pending work so nothing falls through the cracks
Quality Standards
What a Good Trace Looks Like
## Summary
Replaced the polling-based notification system with Server-Sent Events to reduce
server load and deliver real-time updates to the dashboard.
## Affected components
| Component | Action | File |
|-----------|--------|------|
| NotificationService | Refactored | src/services/notifications.ts |
| DashboardView | Modified | src/views/Dashboard.vue |
| EventStream | Added | src/services/event-stream.ts |
## Technical decisions
- SSE over WebSockets: chose SSE because we only need server-to-client push;
WebSockets would add connection management complexity we don't need.
## TODOs
- [ ] Add reconnection logic with exponential backoff to EventStream
- [ ] Write integration test for SSE endpoint under load
What a Bad Trace Looks Like
Changed notifications.ts, Dashboard.vue. Added event-stream.ts. Updated deps.
This is useless. No context on why, no decisions recorded, no actionable follow-up.
Constraints
- Each trace: under 150 lines
- Summary: 2 sentences max, independently understandable
- Every component listed must have an action verb: Added, Modified, Deleted, Refactored
- At least one technical decision with reasoning (chose X because Y)
- TODOs must be specific and actionable (not "clean up later")
- If the trace fails any constraint, revise it before saving
What ships with it
16 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.
- commands/trace-commit.md 907 B
- commands/trace-init.md 1.1 KB
- commands/trace-log.md 725 B
- commands/trace-map.md 891 B
- commands/trace-review.md 859 B
- commands/trace-sync.md 970 B
- commands/trace.md 1.2 KB
- references/component_patterns.md 5.2 KB
- references/drift_detection.md 2.9 KB
- references/sync_strategies.md 4.2 KB
- references/trace_schema.md 3.2 KB
- templates/architecture_overview.md 797 B
- templates/changelog_entry.md 442 B
- templates/component_doc.md 688 B
- templates/readme_section.md 446 B
- templates/session_summary.md 296 B
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.
- 1mo ago First seen · 253 lines · 0 tokens per session scan A 0ecb1734bd15
skill is a skill published in the GitHub repository 888wing/codetape (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,146 tokens. 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.
Other skills, from other repositories
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.