For humans
Ready-made tasks for your assistant
At a glance
6tasks
4run the checklist
3wait for your approval
Task 1
Secure or audit this project
Prompt
Secure this project using the guides at https://github.com/jposluns/secureconfig (see https://secureconfig.ai). Audit it first: list every listening service with its TLS and authentication state, and report the gaps as a table. Propose the fix for each gap per the matching guide (TLS on every endpoint, strong authentication, MFA where viable, and no secrets in the repository) and wait for my approval before changing anything. After approval, apply the fixes, run the README verification checklist, and report anything you could not test.
Task 2
Review the AI and agent stack
Prompt
Review the deployment exposure of this project's AI and agent infrastructure using the guides at https://github.com/jposluns/secureconfig (see https://secureconfig.ai). Inventory every AI-related service present: model servers, inference proxies, vector databases, MCP servers, agent builders, chat and image-generation UIs, notebooks, workflow tools, and observability services. Record each service's transport; for stdio MCP servers and other services with no network listener, mark bind address and TLS not applicable and instead review their inherited credentials and outbound access. For each, report its bind address, TLS state, authentication state, machine credentials, and outbound access to external services and cloud metadata; many of these tools need authentication configured and their defaults vary. Report the gaps as a table and propose the fix for each per the matching guide: loopback binding, a fronting TLS and login layer where there is no native control, scoped API keys, and egress control per egress-metadata.md. Wait for my approval before changing anything, then apply the fixes and run the README verification checklist. Keep the review within deployment exposure.
Task 3
Audit for exposed business rules
Prompt
Audit this project for confidential business rules exposed to the public, using the secret-handling guidance at https://github.com/jposluns/secureconfig (see https://secureconfig.ai), specifically secrets.md and web-exposure.md. A confidential pricing formula, allocation rule, or customer-specific process is protected because it is confidential, not because it is code, so treat it like a secret. Search these three exposure paths: the public repository and its git history, anything that ships to the browser (a NEXT_PUBLIC_ or VITE_ value, logic in client-shipped code, or a source map), and any prompt sent to a public LLM or an API outside your data agreement. Report each exposure as a table with its location and what it reveals, giving the exposure type rather than copying the confidential rule itself into the report. Propose the fix per secrets.md and web-exposure.md: move the rule into server-side code the client only calls, and keep it out of the client bundle and out of public LLM prompts. For anything already published, note that removal is hygiene, not containment, since it does not unpublish what was already public. Wait for my approval before changing anything, then apply the fixes and run the README verification checklist. Keep the review within deployment exposure.
Task 4
Add single sign-on and MFA
Prompt
Add single sign-on to this project using the guides at https://github.com/jposluns/secureconfig (see https://secureconfig.ai). Read identity-providers.md to choose between Google, Microsoft Entra, GitHub, or a hosted customer-identity provider that fits this project's users and budget, then wire it per oidc-integration.md: authorization code with PKCE, exact redirect URIs, token validation, and an allowlist check of the tenant, domain, or group so that a successful login is never treated as authorization. Enforce MFA at the provider, prefer passkeys for administrators, and run the README verification checklist before reporting completion.
Task 5
Check your assistant against AIQT Guardrails
Prompt
Assess this project, and the guardrails you yourself operate under, against the AIQT Guardrails standard at https://github.com/jposluns/guardrails (see https://aiqt.ai). Identify every gap: the accuracy, integrity, verification, and security behaviours the standard requires that this project or your current working rules do not yet meet. Recommend the specific guardrails to adopt, or adoption of the standard as a whole, with the reason for each recommendation.
Task 6
Run a GRC gap assessment
Prompt
Assess this project for governance, risk, compliance, and alignment to the standards covered by the GRC Library at https://github.com/jposluns/grc_library (see https://grclibrary.ai). Identify which of its domains and standards apply, deliver a gap assessment against each applicable control set, and provide either a prioritized improvement plan or an alignment register mapping the project's current state to the applicable controls.