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 laurigates/dotfiles --skill podio-ticket-updatesgit clone --depth 1 https://github.com/laurigates/dotfilesWrote 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/laurigates/dotfiles/podio-ticket-updates)<a href="https://agentmods.dev/skills/laurigates/dotfiles/podio-ticket-updates"><img src="https://agentmods.dev/badge/skills/laurigates/dotfiles/podio-ticket-updates/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/laurigates/dotfiles/podio-ticket-updates"><img src="https://agentmods.dev/badge/skills/laurigates/dotfiles/podio-ticket-updates.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.01440 |
| Opus 5.5 | $0.00024 | $0.00576 |
| Sonnet 5.5 | $0.00012 | $0.00288 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
podio-ticket-updates 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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Podio Ticket Progress Updates
Update my in-progress Podio tickets with progress from linked GitHub repositories.
Configuration
The board coordinates are not stored in this skill. Read them from the
environment (set them in ~/.api_tokens, which mise sources):
printenv PODIO_ORG_LABEL PODIO_SPACE_LABEL PODIO_APP_LABEL PODIO_RESPONSIBLE PODIO_GITHUB_ORG
| Variable | Meaning |
|---|---|
PODIO_ORG_LABEL |
Podio organization URL label |
PODIO_SPACE_LABEL |
Workspace URL label |
PODIO_APP_LABEL |
Kanban app URL label |
PODIO_RESPONSIBLE |
Your display name in Podio, as shown in the Responsible field |
PODIO_GITHUB_ORG |
GitHub org whose repos the tickets track |
The three labels are the path segments of the board URL:
https://podio.com/<org>/<space>/apps/<app>/. If any variable is unset, ask
the user for it before calling the MCP. Do not guess.
Workflow
1. Fetch My In-Progress Tickets
Use mcp__podio-mcp__list_items to get tickets from the Kanban:
- org_label:
$PODIO_ORG_LABEL - space_label:
$PODIO_SPACE_LABEL - app_label:
$PODIO_APP_LABEL - status_filter:
In Progress - responsible_filter:
$PODIO_RESPONSIBLE
responsible_filter has a known bug: it does not match tickets with multiple
assignees. Also fetch without the filter and cross-reference to find all my
tickets.
2. Get Ticket Details
For each ticket, use mcp__podio-mcp__get_item_by_app_item_id to fetch:
- Full description
- Project and Epic assignments
- Any GitHub links in the description
3. Identify Related Repositories
For each ticket, determine the related GitHub repo by:
- Checking for explicit GitHub URLs in the description
- Searching the
$PODIO_GITHUB_ORGorg for repos matching the ticket title keywords - Asking the user if no match is found
4. Fetch Git History
For each identified repo, get recent commits:
gh api "repos/$PODIO_GITHUB_ORG/{repo}/commits" --jq '.[:20] | .[] | "[\(.commit.author.date | split("T")[0])] \(.commit.message | split("\n")[0])"'
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.
- 22d ago First seen · 150 lines · 59 tokens per session scan A c1a81ba40465
podio-ticket-updates is a skill published in the GitHub repository laurigates/dotfiles (10 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,440 once invoked, about $0.0002 per session on Opus 5.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-09-25.
Other skills, from other repositories
work-on
End-to-end workflow for shipping a GitHub issue. Assesses complexity, builds a tailored workflow, and orchestrates skills from research through PR.
acli
Search, plan, and update Atlassian Jira and Confluence with acli.
github-issues
Plan, draft, update, link, and close GitHub issues.
project-manager
Use when creating, updating, or triaging GitHub issues. Writes issues from a product perspective — user stories, acceptance criteria, context, and dependencies — without prescribing implementation.
share-plan
Use when sharing an implementation plan to a GitHub issue. Formats plans with collapsible details sections so issues are scannable but comprehensive.
bf
Search, read, and update Brain Framework brains (bf): project notes, decisions, actions, and collected mail, calendar, Git, chat, and agent-session records.