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 vixues/LeAgent --skill attendance-signin-sheetgit clone --depth 1 https://github.com/vixues/LeAgentWrote 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/vixues/leagent/attendance-signin-sheet)<a href="https://agentmods.dev/skills/vixues/leagent/attendance-signin-sheet"><img src="https://agentmods.dev/badge/skills/vixues/leagent/attendance-signin-sheet/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/vixues/leagent/attendance-signin-sheet"><img src="https://agentmods.dev/badge/skills/vixues/leagent/attendance-signin-sheet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00410 |
| Opus 5 | $0.00026 | $0.00205 |
| Sonnet 5 | $0.00010 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
attendance-signin-sheet 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 11d 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
Attendance / sign-in sheet
Scope
- In scope: printable sign-in / 签到 sheet with people rows and signature columns.
- Out of scope: full attendance anomaly scoring, leave math, or payroll — decline or hand off unless the user explicitly expands scope.
Before generating
If layout/business params are missing, call ask_user alone for 3–5 blockers:
- Meeting / title text (and whether rows 1–3 are print title rows)
- Name source (which attachment / column)
- Sort order (e.g. by department, roster order)
- Row height / grid / print centering (defaults: row height 22, show gridlines, landscape or portrait per user)
- Extra columns (employee id, department, signature, date)
Generate
- Prefer
excel_generatorwith real data rows (never header-only). - If scripting is required, use
code_execution, then cite the managedfile_id/download_urlfrom the tool result (never a sandbox path). - If
quality_passedis false, fill data and regenerate until the download has content rows.
After user corrections
Fold corrected rules (row height, title rows, sort map) back into this skill / procedure memory for the next run — do not only fix the one-off file.
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.
- 11d ago First seen · 46 lines · 51 tokens per session scan A 3c1101524dbf
attendance-signin-sheet is a skill published in the GitHub repository vixues/LeAgent (220 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 410 once invoked, about $0.0003 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
data-analysis
Analyze Excel/CSV files with DuckDB SQL via bash.
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the /rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…