Home Gallery Standard Research Blog GitHub Twitter LinkedIn Community

agent-governance-toolkit system prompt

Category: Coding agents. Audited against the AISPA standard.

What is in agent-governance-toolkit's system prompt?

agent-governance-toolkit's full system prompt: 1 version, 2,821 characters. Audited against AISPA.

The full text of 1 prompt is reproduced below, 2,821 characters in all, each read instruction by instruction against the eight AISPA dimensions. Nothing was flagged as working against the person on the other end.

1 Prompts on record
0 Flagged instructions
AI audit Audit source
D3 · Privacy & Data Protection D4 · Tool/Action Safety

agent-governance-toolkit - policy engine docs llm annotator providers

2821 characters

# LLM annotator provider presets The bundled host side `llm` annotator dispatcher supports several request adapters while preserving one annotation shape. The pure runtime still receives only dispatcher output under `annotations.<name>`. | Provider | Manifest `provider` | Request shape | Response text source | Default credential | | --- | --- | --- | --- | --- | | OpenAI | `openai` | `/v1/chat/completions` with JSON object response format | `choices[0].message.content` | `OPENAI_API_KEY` | | OpenAI compatible | `openai_compatible` | OpenAI chat completions | `choices[0].message.content` | none unless `api_key_env` or `api_key` is set | | Azure OpenAI | `azure_openai` | Azure chat completions deployment URL | `choices[0].message.content` | `AZURE_OPENAI_API_KEY` | | Amazon Bedrock | `bedrock` | Bedrock Converse | `output.message.content[].text` | `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` | | Gemini | `gemini` | `generateContent` with JSON MIME response | `candidates[0].content.parts[].text` | `GEMINI_API_KEY` | | Ollama | `ollama` | `/api/chat` with `format: json` and `stream: false` | `message.content` | none | Every adapter expects the model text to be a JSON object. The dispatcher reads `label` by default or the configured `label_field`, then returns `{"label":"...","raw":"..."}`. Provider transport errors, non 2xx responses, malformed provider JSON, malformed model JSON, and missing labels fail closed as annotator errors. ## Config examples ```yaml annotators: openai_judge: type: llm provider: openai model: gpt-4o-mini api_key_env: OPENAI_API_KEY system_prompt: Respond only with JSON containing {"label":"allow"} or {"label":"deny"}. gateway_judge: type: llm provider: openai_compatible endpoint: http://127.0.0.1:4000/v1/chat/completions model: hosted-judge azure_judge: type: llm provider: azure_openai endpoint: https://example.openai.azure.com deployment: judge-deployment api_version: 2024-02-15-preview api_key_env: AZURE_OPENAI_API_KEY bedrock_judge: type: llm provider: bedrock model: anthropic.claude-3-haiku-20240307-v1:0 aws_region: us-east-1 aws_access_key_id_env: AWS_ACCESS_KEY_ID aws_secret_access_key_env: AWS_SECRET_ACCESS_KEY aws_session_token_env: AWS_SESSION_TOKEN gemini_judge: type: llm provider: gemini model: gemini-1.5-flash api_key_env: GEMINI_API_KEY ollama_judge: type: llm provider: ollama base_url: http://localhost:11434 model: llama3.1 ``` LiteLLM, vLLM, and local gateway deployments should use `openai_compatible` when they expose chat completions. Use `headers` for non secret static headers. Use `provider_config` for provider request fields that are not modeled by ACS, such as Bedrock `inferenceConfig`.

Questions about agent-governance-toolkit's system prompt

Does agent-governance-toolkit's system prompt contain instructions that work against the user?

No. Nothing in agent-governance-toolkit's system prompt was flagged as working against the person the product is talking to. That is a clean result across all eight AISPA dimensions, not an absence of checking — the full text was read instruction by instruction.

How long is agent-governance-toolkit's system prompt?

2,821 characters across 1 prompt on this page. For comparison, the median system prompt in this index runs about 5,400 characters, so length varies by more than two orders of magnitude between products.

How many versions of agent-governance-toolkit's system prompt are on record?

1. Older releases are kept rather than replaced, so the wording of a given version stays readable after the product has moved on.

Where did this agent-governance-toolkit system prompt come from?

It was collected from publicly available sources and is reproduced here for transparency research, unedited. This site does not extract prompts from products itself.

How was agent-governance-toolkit's system prompt audited?

Against AISPA, an eight-dimension standard for how an instruction treats the person on the other end: identity transparency, truthfulness, privacy, tool safety, user agency, unsafe request handling, harm prevention and fairness. This audit was ai audit. The method is described in the paper behind the standard.

How this page was made

The prompt text above is reproduced verbatim from a public source. Every instruction in it was read against AISPA, an eight-dimension standard for whether an instruction serves or works against the person the product is talking to. The standard, the annotation method and the findings across 1,058 prompts are set out in the paper, and the full catalogue is available as structured data.

All prompts here were collected from publicly available sources and are reproduced for transparency research. Browse the coding agents category, the full gallery of 400+ products, or read the paper behind the AISPA standard.