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/jtsang4/efficient-coding/seenpx skills add jtsang4/efficient-coding --skill seegit clone --depth 1 https://github.com/jtsang4/efficient-codingWhat 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.00023 | $0.02040 |
| Opus 5 | $0.00012 | $0.01020 |
| Sonnet 5 | $0.00005 | $0.00408 |
| Haiku 4.5 | $0.00002 | $0.00204 |
Grade A, and why
see scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "https://s.ee/api/v1/shorten" \ How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
S.EE API Skill
S.EE is a URL shortening and content sharing platform with three core services: short URL management, text sharing (code snippets, notes, markdown), and file sharing. Use the following API specifications to call the S.EE REST API on behalf of the user.
Authentication
All API requests require an access token in the Authorization header:
Authorization: Bearer YOUR_ACCESS_TOKEN
Resolve the API key in this order:
- Read the
.envfile in this skill's directory (look forSEE_API_KEY=...) - Check the
$SEE_API_KEYenvironment variable - If neither exists, ask the user for their API key
Base URL: https://s.ee/api/v1
Response Format
All responses follow a standard JSON structure:
{
"code": 200,
"message": "success",
"data": { ... }
}
code200 = successcode400 = invalid request parameterscode401 = missing or expired API keycode500 = server error
Quick Reference: All Endpoints
| Category | Operation | Method | Path |
|---|---|---|---|
| Short URLs | Create | POST | /shorten |
| Short URLs | Create (Simple) | GET | /shorten |
| Short URLs | Update | PUT | /shorten |
| Short URLs | Delete | DELETE | /shorten |
| Short URLs | Get Domains | GET | /domains |
| Short URLs | Visit Stats | GET | /link/visit-stat |
| Text | Create | POST | /text |
| Text | Update | PUT | /text |
| Text | Delete | DELETE | /text |
| Text | Get Domains | GET | /text/domains |
| File | Upload | POST | /file/upload |
| File | History | GET | /files |
| File | Private Download URL | GET | /file/private/download-url |
| File | Delete | GET | /file/delete/{hash} |
| File | Get Domains | GET | /file/domains |
| General | Get Tags | GET | /tags |
| General | Get Usage | GET | /usage |
For detailed parameter specifications of each endpoint, read references/api-details.md.
Short URLs
Create Short URL
curl -X POST "https://s.ee/api/v1/shorten" \
-H "Authorization: Bearer $SEE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"target_url": "https://example.com/long-url",
"domain": "s.ee"
}'
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.
- yesterday First seen · 274 lines · 23 tokens per session scan A 94d1afc95d21
see is a skill published in the GitHub repository jtsang4/efficient-coding (2 stars, last pushed 7d ago), licensed MIT. It adds 23 tokens to every session and 2,040 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…