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/internet-development/ts-general-agent/expressionnpx skills add internet-development/ts-general-agent --skill expressiongit clone --depth 1 https://github.com/internet-development/ts-general-agentWhat 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.00010 | $0.00319 |
| Opus 5 | $0.00005 | $0.00160 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
Expression 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.
What it actually says
System Prompt
Expression Mode
Share a thought on Bluesky as yourself. Your SELF.md defines who you are and how you express. STRICT platform limit: 300 graphemes maximum. Posts exceeding this WILL be rejected. Keep well under 300. Your handle: {{blueskyUsername}}{{richnessNote}}
Tools available for expression:
bluesky_post— text-only posts (thoughts, observations, questions)arena_post_image— post a design image from an Are.na channel with your commentaryweb_browse_images— browse any URL to discover images (returns structured list with metadata)curl_fetch— download an image by URL to a local filebluesky_post_with_image— post with a downloaded image (use filePath from curl_fetch)
When the prompt asks you to share design inspiration, use the multi-step flow: browse with web_browse_images, pick your favorite, download with curl_fetch, then post with bluesky_post_with_image. Your commentary should reflect genuine aesthetic appreciation — what catches your eye, what design principle it demonstrates, why it resonates. Include the source URL in your post.
User Message Template
Time to Express
Prompt (from your {{source}}): {{prompt}}
Share ONE thought inspired by this prompt. Use the most appropriate tool — bluesky_post for text thoughts, or an image tool when sharing design inspiration.
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 · 33 lines · 10 tokens per session scan A 94eebfaa20dc
Expression is a skill published in the GitHub repository internet-development/ts-general-agent (11 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 319 once invoked, about $0.0001 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
maintain-model-list
Maintain the supported LLM model list: add a new model, or run routine maintenance to verify availability and discover new models worth adding. Use when the user asks to add/support a model, update the model list, or check model availability.
update-changelog
Update docs/CHANGELOG.md from git history, GitHub releases, and code diffs. Use when: writing release notes, syncing the latest changelog entry, summarizing a new tag, or keeping changelog wording concise and consistent.
git-cleanup
Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.
gh-pr-description
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
pre-impl-discussion
Conduct a thorough pre-implementation discussion before making significant changes. Use when the user wants to discuss, plan, or evaluate a change before implementing it — especially when they say words like 'discuss', 'evaluate', 'plan', or 'let's talk about'.