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 yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server --skill recent-recordsgit clone --depth 1 https://github.com/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-serverWrote 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/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/recent-records)<a href="https://agentmods.dev/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/recent-records"><img src="https://agentmods.dev/badge/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/recent-records/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/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/recent-records"><img src="https://agentmods.dev/badge/skills/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/recent-records.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.00175 | $0.01708 |
| Opus 5 | $0.00088 | $0.00854 |
| Sonnet 5 | $0.00035 | $0.00342 |
| Haiku 4.5 | $0.00017 | $0.00171 |
Grade A, and why
recent-records 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 10d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recent Records
Answer "what's the latest / most recent / last X" questions for any Acumatica entity, reliably.
Why this skill exists
Many Acumatica tenants silently ignore $orderby - passing orderby="Date desc" does nothing, and
list_records returns rows in arbitrary (effectively oldest-first) order. So the obvious approach -
"list the entity, sort by date, take the top one" - quietly returns the wrong record. Users rarely
notice, which makes it worse: they get a confidently-presented sales order from 2021 when they asked
for the newest one.
The fix is to filter to a recent date window, then sort the small result client-side. The API
honors $filter perfectly even though it ignores $orderby. This skill encodes that pattern plus the
two things people get wrong around it: which date field to use, and the exact datetime literal format.
The procedure
1. Pin down the entity and the date field
Map the user's words to an entity (e.g. "PO" -> PurchaseOrder, "bill" -> Bill, "the latest order"
in a sales context -> SalesOrder). Then call describe_entity(entity) to get the real field
names - a guessed field name causes a hard HTTP 500, so never assume them.
Pick the date field from the user's intent, not just availability:
| The user means... | Words that signal it | Use this field |
|---|---|---|
| Most recently created / entered / placed / dated | "latest", "last one we entered", "newest", "just came in" | the document date - usually Date (some entities use OrderDate, DocDate) |
| Most recently changed / touched / updated | "recently modified", "last updated", "changed since..." | LastModifiedDateTime |
When it's genuinely ambiguous, default to the document date (Date) and break ties with
LastModifiedDateTime - that matches what people usually mean by "the latest one." If the document
date field isn't obvious from describe_entity, LastModifiedDateTime is a safe fallback that exists
on virtually every entity.
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.
- 10d ago First seen · 129 lines · 175 tokens per session scan A a90ce9883573
recent-records is a skill published in the GitHub repository yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server (0 stars, last pushed 27d ago), licensed MIT. It adds 175 tokens to every session and 1,708 once invoked, about $0.0009 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-09-01.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…