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 whistlegraph/aesthetic-computer --skill whistlegraphgit clone --depth 1 https://github.com/whistlegraph/aesthetic-computerWrote 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/whistlegraph/aesthetic-computer/whistlegraph)<a href="https://agentmods.dev/skills/whistlegraph/aesthetic-computer/whistlegraph"><img src="https://agentmods.dev/badge/skills/whistlegraph/aesthetic-computer/whistlegraph/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/whistlegraph/aesthetic-computer/whistlegraph"><img src="https://agentmods.dev/badge/skills/whistlegraph/aesthetic-computer/whistlegraph.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.00026 | $0.00469 |
| Opus 5.5 | $0.00010 | $0.00188 |
| Sonnet 5.5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
whistlegraph 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.
What it actually says
Whistlegraph Desk
Use the whistlegraph_* MCP tools whenever the user asks to inspect, edit, commit,
publish, deploy, or roll forward the Whistlegraph frontend. Do not substitute raw
shell Git commands for the publishing tools.
The user must run Codex from an aesthetic-computer checkout whose origin can
push to the Tangled knot. Authentication comes from the shared Aesthetic Computer
session in ~/.ac-token; if it is absent or expired, tell the user to run
ac-login and retry.
Frontend change workflow
- Call
whistlegraph_whoamiand confirm the server grants maintainer access. - Call
whistlegraph_begin_changewith a short summary. This creates an isolated worktree from the currentorigin/main; it never uses or alters the user's working tree. - Inspect with
whistlegraph_list_frontend,whistlegraph_read_frontend, andwhistlegraph_diff_change. - Edit only through
whistlegraph_replace_frontendorwhistlegraph_write_frontend. The server is intentionally limited tosystem/public/whistlegraph.org/**. - Call
whistlegraph_validate_change. Resolve every reported error before publishing. - Show the user the final diff summary and ask for explicit confirmation before
calling
whistlegraph_publish_changeunless the user already explicitly asked to publish. - Publishing creates a normal attributed commit, pushes its review branch,
fast-forwards
mainonly if the original base is still current, and asks the Auth0-protected Desk endpoint to deploy that exact SHA.
If main moved, begin a fresh change and reapply the desired edit. Never force
push, reset shared history, bypass validation, edit outside the allowlist, or ask
for deployment secrets.
Archive metadata edits remain available in the web Desk at https://whistlegraph.org/desk. This first MCP release focuses on frontend files and the Git/deployment path.
What ships with it
1 file 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.
- 2mo ago First seen · 44 lines · 26 tokens per session scan A dec3f6f039ab
whistlegraph is a skill published in the GitHub repository whistlegraph/aesthetic-computer (91 stars, last pushed today), licensed ISC. It adds 26 tokens to every session and 469 once invoked, about $0.0001 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-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.