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/gotempsh/temps/add-error-trackingnpx skills add gotempsh/temps --skill add-error-trackinggit clone --depth 1 https://github.com/gotempsh/tempsWhat 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.00182 | $0.04435 |
| Opus 5 | $0.00091 | $0.02218 |
| Sonnet 5 | $0.00036 | $0.00887 |
| Haiku 4.5 | $0.00018 | $0.00443 |
Grade A, and why
add-error-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 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 — 563 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Error Tracking
Integrate Temps error tracking (Sentry-compatible) into an application. The Temps DSN is a drop-in replacement for a Sentry DSN — use the official Sentry SDK for the user's platform and point it at the Temps DSN via an environment variable.
Prefer Sentry's official per-framework skills when available
Temps is Sentry wire-compatible, so every skill Sentry publishes for their SDKs works against a Temps DSN. If the user's CLI already has one of these installed, route them to it and only substitute the DSN:
| User's platform | Sentry skill | Source |
|---|---|---|
| Next.js | /sentry-nextjs-sdk |
getsentry/sentry-for-ai |
| React (Vite, Remix, etc.) | /sentry-react-sdk |
getsentry/sentry-for-ai |
| Vanilla browser JS | /sentry-browser-sdk |
getsentry/sentry-for-ai |
| Node.js | /sentry-node-sdk |
getsentry/sentry-for-ai |
| React Native | /sentry-react-native-sdk |
getsentry/sentry-for-ai |
| Generic (language-agnostic) | /sentry-sdk-setup |
getsentry/sentry-for-ai |
For platforms Sentry has no dedicated skill for (Vue, Svelte, Angular, Python, Go, Rust, Ruby, Java, PHP, .NET, Flutter, etc.), follow the setup in this file directly.
Always set the DSN from an environment variable — never hardcode it. The user will point the env var at their Temps DSN instead of a Sentry DSN.
Detect the platform
Infer the platform from the codebase:
package.jsonwith"next"→ Next.js →@sentry/nextjspackage.jsonwith"react"and Vite/Remix/CRA → React →@sentry/reactpackage.jsonwith"vue"or"nuxt"→ Vue →@sentry/vuepackage.jsonwith"svelte"or"@sveltejs/kit"→ Svelte →@sentry/sveltekitpackage.jsonwith"@angular/core"→ Angular →@sentry/angularpackage.jsonwith"express","fastify","@nestjs/core"→ Node.js →@sentry/nodepackage.jsonwith"react-native"or"expo"→ React Native →@sentry/react-nativerequirements.txt/pyproject.tomlwith Flask, Django, FastAPI → Python →sentry-sdkgo.mod→ Go →github.com/getsentry/sentry-goCargo.toml→ Rust →sentryGemfilewithrails→ Ruby →sentry-ruby+sentry-railspom.xml/build.gradlewith Spring → Java →sentry-spring-boot-starter-jakartacomposer.jsonwithlaravel/frameworkorsymfony/*→ PHP →sentry/sentry.csprojwithMicrosoft.AspNetCore.*→ .NET →Sentry.AspNetCorepubspec.yamlwithflutter→ Flutter →sentry_flutter
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 · 563 lines · 182 tokens per session scan A 48c687de06a1
add-error-tracking is a skill published in the GitHub repository gotempsh/temps (700 stars, last pushed 2d ago), licensed Apache-2.0. It adds 182 tokens to every session and 4,435 once invoked, about $0.0009 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
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
project-snmp-profiles-authoring
Use when editing Netdata SNMP profile YAMLs, topology SNMP profiles, ddsnmp profile parsing, or profile-format documentation. Requires checking source MIB field accessibility, especially MAX-ACCESS not-accessible INDEX objects, before adding or changing profile symbols.
fix-issues
Fix a batch of open GitHub issues end to end - one git worktree and one agent per issue (feature-dev for implementation, review-pr for review), individual PRs into develop, a release PR to main with a final multi-agent integration review, and optional tag/release/issue-comment publishing. Use when the user asks to…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
kurtosis-ethereum
Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package. Use for spinning up local devnets, syncing public testnets, validating cross-client interop, testing fork transitions, shadowforks, running assertoor checks, debugging CL/EL client interactions, or verifying new feature…