Borrowing it
Nothing to install: this file belongs to daryllabar/XrmUnitTest. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/daryllabar/XrmUnitTest/master/.cursor/skills/generate-ids/SKILL.mdgit clone --depth 1 https://github.com/daryllabar/XrmUnitTestWrote 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/daryllabar/xrmunittest/generate-ids)<a href="https://agentmods.dev/skills/daryllabar/xrmunittest/generate-ids"><img src="https://agentmods.dev/badge/skills/daryllabar/xrmunittest/generate-ids/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/daryllabar/xrmunittest/generate-ids"><img src="https://agentmods.dev/badge/skills/daryllabar/xrmunittest/generate-ids.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.00047 | $0.00867 |
| Opus 5 | $0.00023 | $0.00434 |
| Sonnet 5 | $0.00009 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
generate-ids 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 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.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate DataverseUnitTest IDs
Use the Id Generator CLI instead of hand-writing GUIDs or guessing naming rules.
Documentation: Id Generator wiki · Id Generator CLI wiki
Install (NuGet)
dotnet tool install -g DataverseUnitTest.IdGenerator.Cli
NuGet: DataverseUnitTest.IdGenerator.Cli
Requires .NET 10 SDK or runtime (or newer).
When to use
- Adding or extending test classes with
Id<T>properties - Creating nested
*Idshelper classes for test data - Regenerating GUIDs while preserving existing structure
Preferred command
If the global tool is installed from NuGet:
idgen --settings-file .cursor/IdGeneratorSettings.json --input "Account 2|Contact"
When working in the source repository without the global tool:
dotnet run --project IdGenerator.Cli -- --settings-file .cursor/IdGeneratorSettings.json "Account 2|Contact"
Input format
Each non-empty line defines IDs for one Early Bound entity type. On the command line, use | instead of a newline.
Examples:
Account
Account 2
Acme_ProjectTask,Task
Contact,Partners,Jim,Bob
Account 2|Contact,Partners,Jim,Bob
Rules:
- First token is the entity type (
Account,Contact,Acme_Project, etc.) - Space format:
<EntityType> [Count] - Comma format:
<EntityType>,<NameOrCollection>[,<IdName1>,...] - Do not put spaces after commas inside comma-based tokens
Modes
Generate from entity input
idgen --settings-file .cursor/IdGeneratorSettings.json --input "Account|Contact 2"
Regenerate from existing C#
Parse an existing test ID block and regenerate GUIDs with the same shape:
idgen --settings-file .cursor/IdGeneratorSettings.json --from-csharp TestExample.TestMethodNameClass.TestIds path/to/TestFile.cs
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 · 122 lines · 47 tokens per session scan A 6240c15376fd
generate-ids is a skill published in the GitHub repository daryllabar/XrmUnitTest (61 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 867 once invoked, about $0.0002 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-04.
Other skills, from other repositories
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
migrate-mstest-v3-to-v4
Use this skill before answering, planning, or editing any MSTest 3.x-to-4.x upgrade or post-upgrade failure. Triggers include "MSTest v4 breaking changes"; CS0507/CS0103/CS1061/CS1615; ExecuteAsync, CallerInfo, DisplayName, or custom TestMethodAttribute; ClassCleanupBehavior; ContainsKey; ThrowsExactly or…
migrate-mstest-v1v2-to-v3
Use this skill before answering or editing whenever an MSTest v1/v2 project is being upgraded or repaired for v3. Triggers include QualityTools assembly references; MSTest.TestFramework/TestAdapter 1.x-2.x; "upgrade to MSTest v3"; comparing v1 and v2 migration paths; choosing MSTest or MSTest.Sdk; CS0411/CS1503 after…
writing-mstest-tests
ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for "review" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected/actual labels…
migrate-xunit-to-mstest
Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…