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 aiocean/claude-plugins --skill aio-tancagit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-tanca)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-tanca"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-tanca.svg" alt="Measured on agentmods" 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.00025 | $0.01030 |
| Opus 5 | $0.00013 | $0.00515 |
| Sonnet 5 | $0.00005 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade B, and why
aio-tanca scanned grade B 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 4d 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- MCP configured: !`cat .mcp.json 2>/dev/null | grep -q tanca && echo "YES" || echo "NO"` How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tanca Skill
Employee timekeeping and HR operations via nguyenvanduocit/tanca-mcp.
Environment
- Go: !
which go 2>/dev/null || echo "NOT INSTALLED" - tanca-mcp: !
which tanca-mcp 2>/dev/null || echo "NOT INSTALLED" - tanca-cli: !
which tanca-cli 2>/dev/null || echo "NOT INSTALLED" - TANCA_TOKEN: !
[ -n "$TANCA_TOKEN" ] && echo "SET" || echo "NOT SET" - TANCA_SHOP_ID: !
echo ${TANCA_SHOP_ID:-NOT SET} - TANCA_BRANCH_ID: !
echo ${TANCA_BRANCH_ID:-NOT SET} - MCP configured: !
cat .mcp.json 2>/dev/null | grep -q tanca && echo "YES" || echo "NO"
Install (skip if already installed above)
go install github.com/nguyenvanduocit/tanca-mcp@latest
go install github.com/nguyenvanduocit/tanca-mcp/cmd/tanca-cli@latest
Add to .mcp.json:
{
"mcpServers": {
"tanca": {
"command": "tanca-mcp",
"env": {
"TANCA_TOKEN": "Bearer your-token-here",
"TANCA_SHOP_ID": "12345"
}
}
}
}
Values needed: TANCA_TOKEN (format: Bearer your-token-here), TANCA_SHOP_ID (auto-fetched if omitted), TANCA_BRANCH_ID (optional). Restart Claude Code after configuring.
MCP Tools (prefix: tanca_)
Employee Management
| Tool | Usage |
|---|---|
tanca_list_employees |
() — all employees |
tanca_list_timekeeping_employees |
() — employees requiring timekeeping |
Shift Management
| Tool | Usage |
|---|---|
tanca_list_shifts |
() — all shift assignments |
tanca_get_shift_summary |
(employee_id: "123") |
tanca_get_today_shift |
(employee_id: "123") |
Check-in / Check-out
tanca_check_in(employee_id: "123")
tanca_check_out(employee_id: "123")
Clock Logs
tanca_get_clock_logs(employee_id: "123", from: "2025-01-01", to: "2025-01-31")
Shop Info
tanca_get_shop_info()
CLI (fallback if MCP not configured)
tanca-cli list-employees --env .env
tanca-cli list-timekeeping-employees --env .env
tanca-cli list-shifts --env .env
tanca-cli get-shift-summary --employee-id 123 --env .env
tanca-cli get-today-shift --employee-id 123 --env .env
tanca-cli check-in --employee-id 123 --env .env
tanca-cli check-out --employee-id 123 --env .env
tanca-cli get-clock-logs --employee-id 123 --from 2025-01-01 --to 2025-01-31 --env .env
tanca-cli get-shop-info --env .env
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.
- 4d ago First seen · 112 lines · 25 tokens per session scan B 3dc3b34038f1
aio-tanca is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 1,030 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
rtk-optimizer
Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
handoff-update
Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.