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/hipson47/hipson/sentrynpx skills add Hipson47/Hipson --skill sentrygit clone --depth 1 https://github.com/Hipson47/HipsonWhat 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.00046 | $0.01001 |
| Opus 5 | $0.00023 | $0.00500 |
| Sonnet 5 | $0.00009 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade C, and why
sentry scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
1. Install the Sentry CLI: `curl https://cli.sentry.dev/install -fsS | bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Install the Sentry CLI: `curl https://cli.sentry.dev/install -fsS | bash` This is a copy
100% identical to sentry — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry (Read-only Observability)
Quick start
- If not already authenticated, ask the user to run
sentry auth loginor setSENTRY_AUTH_TOKENas an env var. - The CLI auto-detects org/project from DSNs in
.envfiles, source code, config defaults, and directory names. Only specify<org>/<project>if auto-detection fails or picks the wrong target. - Defaults: time range
24h, environmentproduction, limit 20. - Always use
--jsonwhen processing output programmatically. Use--json --fieldsto select specific fields and reduce output size. - Use
sentry schema <resource>to discover API endpoints quickly.
If the CLI is not installed, give the user these steps:
- Install the Sentry CLI:
curl https://cli.sentry.dev/install -fsS | bash - Authenticate:
sentry auth login - Confirm authentication:
sentry auth status
- Never ask the user to paste the full token in chat. Ask them to set it locally and confirm when ready.
Core tasks (use Sentry CLI)
Use the sentry CLI for all queries. It handles authentication, org/project detection, pagination, and retries automatically. Use --json for machine-readable output.
1) List issues (ordered by most recent)
sentry issue list \
--query "is:unresolved environment:production" \
--period 24h \
--limit 20 \
--json --fields shortId,title,priority,level,status
If auto-detection doesn't resolve org/project, pass them explicitly:
sentry issue list {your-org}/{your-project} \
--query "is:unresolved environment:production" \
--period 24h \
--limit 20 \
--json
2) Resolve an issue short ID to issue detail
sentry issue view {ABC-123} --json
Use the short ID format (e.g., ABC-123), not the numeric ID.
3) Issue detail
sentry issue view {ABC-123}
4) Issue events
sentry issue events {ABC-123} --limit 20 --json
5) Event detail
sentry event view {your-org}/{your-project}/{event_id} --json
6) AI-powered root cause analysis
What ships with it
4 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.
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 · 121 lines · 46 tokens per session scan C 508c6f5c1005
sentry is a skill published in the GitHub repository Hipson47/Hipson (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,001 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 100% identical to sentry, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
add-agent-support
Create and ship AgentSessions support for a new or changed local AI agent/provider. Use when adding, reviewing, testing, documenting, or marketing a provider integration, session parser, transcript source, support-matrix entry, verified-version bump, or provider UI surface; drives the full loop from pre-support…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.