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 actinon-com/brass-monkey --skill odoo-attendancegit clone --depth 1 https://github.com/actinon-com/brass-monkeyWrote 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/actinon-com/brass-monkey/odoo-attendance)<a href="https://agentmods.dev/skills/actinon-com/brass-monkey/odoo-attendance"><img src="https://agentmods.dev/badge/skills/actinon-com/brass-monkey/odoo-attendance.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.00028 | $0.00453 |
| Opus 5 | $0.00014 | $0.00227 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
odoo-attendance 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 8d 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
Skill: Odoo Attendance
This skill provides the agent with functional expertise in Odoo's Attendance module, covering check-in/out logs, working hour verification, and overtime management.
Core Mandates
1. Attendance Lifecycle
- Record (
hr.attendance): A simple log with acheck_inand optionalcheck_outdatetime. - Open Sessions: An employee can only have ONE record with an empty
check_outat any time. This represents a currently "Checked In" status. - Mandate: Always verify the
attendance_stateon thehr.employeerecord before attempting to create a new check-in or update a check-out.
2. Overtime & Verification
- Worked Hours: Automatically calculated as the difference between
check_inandcheck_out. - Expected Hours: Pulled from the employee's Working Schedule (
resource.calendar) via their contract. - Overtime: Calculated as
Worked Hours - Expected Hours. The agent should checkovertime_statusto see if extra hours require manager approval.
3. Kiosk Mode & Security
- Authentication: In Kiosk mode, employees use a
pinorbarcode(on thehr.employeemodel) to authenticate. - Data Integrity: Mandate that agents do not manually create overlapping attendance records, as this will break Odoo's internal hour reporting.
4. Search Workflow
- Status Check: Search
hr.employeeto find the currentattendance_state. - Log Review: Query
hr.attendancefiltered byemployee_idandcheck_indate range. - Overtime Audit: Check the
total_overtimecomputed field on the employee record for a historical summary.
Available Resources
attendance-logic.md: Deep-dive into Overtime calculations, Kiosk configuration, and Attendance vs. Timesheets.attendance-fields.json: Dense technical map of fields for Attendance and Employee presence.
What ships with it
2 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.
- 8d ago First seen · 33 lines · 28 tokens per session scan A eb3ed74c9035
odoo-attendance is a skill published in the GitHub repository actinon-com/brass-monkey (2 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 453 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-31.
Other skills, from other repositories
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
spk-run-verdict-capture
Set a Spec Kitty work-package review verdict through the deterministic event-log seam, so every agent harness records approve/reject the same way.
spk-run-implement-review
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
spk-team-sync
Operate Spec Kitty tracker sync (sync pull/sync push/sync run for local providers) and hosted SaaS-backed mission data.
spk-admin-dashboard
Open or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views.